Multi-entity management of a node in a wireless node network

ABSTRACT

Methods and apparatus are disclosed for multi-entity management of an ID node in a wireless node network. The ID node associates with a first entity user access device, which operates as a master node and communicates directly with a server over a first communication path. The first device separately communicates with the ID node over a second communication path, but the ID node is unable to directly communicate with the server. The ID node provides the first device with access to data collected by the ID node if an initial privilege authorizes it. After associating with a shipping entity master node, the ID node provides the shipping entity master node with the data collected based on a transferred privilege from the server. And then after associating with a second entity user access device, the ID node provides access to this second device if authorized by a destination privilege from the server.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application claims the benefit of priority to U.S.Provisional Patent Application Ser. No. 61/910,202 filed on Nov. 29,2013 and to U.S. Provisional Patent Application Ser. No. 62/003,566filed on May 28, 2014.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to systems, apparatus andmethods in the field of tracking items (e.g., an object, a package, aperson, a piece of equipment) and, more particularly, to various aspectsinvolving systems, apparatus and methods for improved assetidentification, location services, and node management using anadaptive, context-aware wireless node network.

BACKGROUND

Asset management has always been an important part of commerce, and theability to identify an item and locate its whereabouts may be consideredcore to companies that ship items from one location to another. Forexample, tracking packages is important to organizations of all kinds,whether it be a company keeping track of inventory to be sold in itsstores, or a package delivery provider keeping track of packages beingtransported through its delivery network. To provide quality service, anorganization typically creates and maintains a highly organized networkfor tracking its items—packages, people, objects, etc. Effectivemanagement of such networks allows lower cost, reduced delivery time,and enhanced customer service. And efficient deployment of the networkhelps manage costs.

In addition to tracking packages, parties that ship and receive packagesmay also need information regarding the conditions of the packages, suchas the temperature and humidity of the package. For example, a customerthat has ordered a box of wine may want to monitor the temperature ofthe contents of the box to determine if the temperature and/or humiditygoes above or below a set range. Likewise, the party that ships thepackage may also want to monitor the conditions of the package to ensurethat the content arrives in the proper condition.

Conventionally, this tracking function may be provided by a variety ofknown mechanisms and systems. Machine-readable barcodes are one wayorganizations keep track of items. A retailer, for example, may use barcodes on items in its inventory. For example, items to be sold in aretailer's store may each be labeled with a different machine-readablebar code. In order to keep track of inventory, the retailer typicallyscans or otherwise captures an image of the bar code on each item sothat a back-end part of the retailer's operation can keep track of whatis coming in and leaving their possession from suppliers. In addition,when an item is sold to a consumer, the bar code for that item isscanned or captured to track sales and inventory levels.

Similarly, a package delivery provider may utilize machine-readable barcodes by associating a bar code with packages to be delivered to arecipient. For example, a package may have a bar code corresponding to atracking number for that package. Each time the package goes through atransit checkpoint (e.g., the courier taking initial control of thepackage, the package being temporarily placed in a storage facilitywhile being moved from a pickup point to a delivery location, and thepackage being delivered to the recipient, etc.), the package's bar codemay be scanned. Bar codes, however, have the disadvantage that personnelmust manually scan each bar code on each item in order to effectivelytrack the items.

Radio-frequency identification (RFID) tags are another known mechanismfor tracking items. In contrast to barcodes, RFID tags do not usuallyrequire manual scanning. For example, in a retail context, an RFID tagon an inventory item may be able to communicate with an electronicreader that detects items in a shopping cart and adds the cost of eachitem to a bill for the consumer. The RFID tag usually transfers a codednumber when queried or prompted by the reader. RFID tags have also beenused to track items such as livestock, railroad cars, trucks, and evenairline baggage. These tags typically only allow for basic tracking, butdo not provide a way to improve asset management using information aboutthe environment in which the items are tracked.

Sensor-based tracking systems are also known which can provide moreinformation than RFID systems. Shippers, carriers, recipients, and otherparties often wish to know the location, condition, and integrity ofshipments before, during, and after transport to satisfy quality controlgoals, meet regulatory requirements, and optimize business processes.However, such systems are typically expensive given the complexity ofthe sensors, and may provide extraneous and redundant item information.

To address these requirements, a system is needed that may monitor dataregarding objects (such as shipped items, personnel, or equipment) andefficiently extend visibility of such objects. Thus, there remains aneed for an improved system that may provide more extensive and robustidentification, tracking, and management of objects and do so in a costeffective manner.

SUMMARY

In the following description, certain aspects and embodiments willbecome evident. It should be understood that the aspects andembodiments, in their broadest sense, could be practiced without havingone or more features of these aspects and embodiments. It should beunderstood that these aspects and embodiments are merely exemplary.

In the following description, certain aspects and embodiments willbecome evident. It should be understood that the aspects andembodiments, in their broadest sense, could be practiced without havingone or more features of these aspects and embodiments. It should beunderstood that these aspects and embodiments are merely exemplary.

One aspect of the disclosure relates to a method for multi-entitymanagement of an ID node in a wireless node network. In this aspect, themethod generally has the ID node associate with a first entity useraccess device. The first entity user access device operates as a masternode in the network and can communicate directly with a server in thenetwork over a first communication path. The first entity user accessdevice separately communicates with the ID node over a secondcommunication path, while the ID node can communicate directly with thefirst entity user access device over the second communication path butis unable to directly communicate with the server. The method proceedswith the ID node providing the associated first entity user accessdevice with access to data collected by the ID node if authorized by aninitial privilege. The ID node then associates with a shipping entitymaster node in the network. The ID node then provides the associatedshipping entity master node with access to the data collected by the IDnode based upon a transferred privilege, which is provided by the serverto the shipping entity master node. The method then has the ID nodeassociating with a second entity user access device. Then, the methodconcludes with the ID node providing the associated second entity useraccess device with access to the data collected by the ID node ifauthorized by a destination privilege, which is provided by the serverto the second entity user access device.

And in a related aspect of the disclosure, a non-transitorycomputer-readable medium is disclosed that contains instructions, whichwhen executed on a processor, performs a method for multi-entitymanagement of a node in a wireless node network. In this aspect, themethod may operate as disclosed above.

Another aspect of the disclosure relates to an additional method formulti-entity management of an ID node in a wireless node network. Inthis aspect, the additional method generally has a first entity useraccess device executing a program module of code to enable the firstentity user access device to operate as a master node that cancommunicate directly with a server over a first communication path andseparately communicate with the ID node over a second communicationpath. The ID node is operative to communicate directly with the firstentity user access device over the second communication path but unableto directly communicate with the server. The method proceeds with thefirst entity user access device transmitting a request to the server,where the request is for an authorization to associate with the ID node.The request also is for an initial privilege related to data to becollected by the ID node. The method continues with the first entityuser access device receiving the authorization and the initial privilegefrom the server, and then associating the first entity user accessdevice with the ID node. Thereafter, the first entity user access devicereceives data collected by the ID node if authorized by the initialprivilege. The method concludes with the first entity user access devicemanaging the data collected by the ID node.

Still another aspect of the disclosure relates to a further method formulti-entity management of an ID node in a wireless node network. Inthis aspect, the further method generally has a recipient entity useraccess device executing a program module of code to enable operation ofthe recipient entity user access device as a master node. As such, therecipient entity user access device is made operative to communicatedirectly with a server over a first communication path and separatelycommunicate with the ID node over a second communication path. The IDnode is operative to communicate directly with the recipient entity useraccess device over the second communication path but unable to directlycommunicate with the server. This further method proceeds with therecipient user access device transmitting a request to the server. Therequest is for an authorization to associate with the ID node. Therequest is also for a destination privilege related to data to becollected by the ID node. The method continues with the recipient useraccess device receiving the authorization and the destination privilegefrom the server, and associating the recipient user access device withthe ID node. The method concludes with the recipient user access devicereceiving data collected by the ID node if authorized by the destinationprivilege.

In yet another aspect of the disclosure, an ID node managed by multipleentities using a wireless node network is described. In this aspect, theID node generally includes a node processing unit, a node memory, and ashort-range communication interface. The node memory and communicationinterface are each coupled to the processing unit. The node memorymaintains code for execution by the processing unit and data collectedby the ID node during operations of the node. The short-rangecommunication interface is operative to directly communicate with amaster node in the network over a short-range communication path butunable to directly communicate with a server in the network.

When executing the node maintained on the node memory, the nodeprocessing unit is specially adapted and operative to cause the ID nodeto operate in a specific, novel, and advantageous manner with otherdevices. In more detail, the node processing unit is programmaticallyoperative to associate the ID node with a first entity user accessdevice, where the first entity user access device operates as the masternode and is operative to communicate directly with the server over alonger range communication path and separately communicate with the IDnode over the short-range communication path; provide the first entityuser access device with access to the data collected by the ID node ifauthorized by an initial privilege, where the initial privilege wasprovided by the server to the first entity user access device; associatethe ID node with a shipping entity master node in the network; providethe associated shipping entity master node with access to the datacollected by the ID node based upon a transferred privilege, where thetransferred privileged was provided by the server to the shipping entitymaster node; associate the ID node with a second entity user accessdevice, where the second entity user access device operates as anothermaster node and is operative to communicate directly with the serverover the longer range communication path and separately communicate withthe ID node over the short-range communication path; and provide theassociated second entity user access device with access to the datacollected by the ID node if authorized by a destination privilegeprovided by the server to the second entity user access device.

Each of these aspects respectively effect improvements to howinformation may be shared and managed when using a network ofinteractive wireless nodes in applications such as logistics, shippingmanagement, inventory management, and the like. Additional advantages ofthis and other aspects of the disclosed embodiments and examples will beset forth in part in the description which follows, and in part will beobvious from the description, or may be learned by practice of theinvention. It is to be understood that both the foregoing generaldescription and the following detailed description are exemplary andexplanatory only and are not restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate several embodiments according toone or more principles of the invention and together with thedescription, serve to explain one or more principles of the invention.In the drawings,

FIG. 1 is a diagram of an exemplary wireless node network in accordancewith an embodiment of the invention;

FIG. 2 is a more detailed diagram of an exemplary wireless node networkin accordance with an embodiment of the invention;

FIG. 3 is a more detailed diagram of an exemplary ID node device inaccordance with an embodiment of the invention;

FIG. 4 is a more detailed diagram of an exemplary master node device inaccordance with an embodiment of the invention;

FIG. 5 is a more detailed diagram of an exemplary server in accordancewith an embodiment of the invention;

FIG. 6 is a diagram illustrating the structure or format of an exemplaryadvertisement data packet in accordance with an embodiment of theinvention;

FIG. 7 is a diagram illustrating sample content for an exemplaryadvertisement data packet in accordance with an embodiment of theinvention;

FIG. 8 is a state diagram illustrating exemplary states and transitionsbetween the states as part of operations by an exemplary node in awireless node network in accordance with an embodiment of the invention;

FIG. 9 is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary master-to-ID node association in accordancewith an embodiment of the invention;

FIG. 10 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary ID-to-ID node association in accordancewith an embodiment of the invention;

FIG. 11 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary ID-to-master node query in accordancewith an embodiment of the invention;

FIG. 12 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary alert advertising mode in accordancewith an embodiment of the invention;

FIG. 13 is a diagram illustrating an exemplary location determinationusing master node advertise in accordance with an embodiment of theinvention;

FIG. 14 is a diagram illustrating an exemplary location determinationusing ID node advertise in accordance with an embodiment of theinvention;

FIG. 15 is a diagram illustrating an exemplary location determinationthrough triangulation in accordance with an embodiment of the invention;

FIG. 16 is a diagram illustrating an exemplary location determinationthrough chaining triangulation in accordance with an embodiment of theinvention;

FIG. 17 is a diagram illustrating an example logistics operation usingexemplary components of a wireless node network in accordance with anembodiment of the invention;

FIG. 18 is a flow diagram illustrating an example method for managingshipment of an item using a wireless node network in accordance with anembodiment of the invention;

FIG. 19 is a flow diagram illustrating another example method formanaging shipment of an item using a wireless node network in accordancewith an embodiment of the invention;

FIG. 20 is a flow diagram illustrating an example method for dynamicallychanging an operational mode of node operations in a wireless nodenetwork in accordance with an embodiment of the invention;

FIG. 21 is a flow diagram illustrating an example method for managing adynamically changing operational mode of node operations in a wirelessnode network in accordance with an embodiment of the invention;

FIGS. 22A-22C are diagrams illustrating exemplary stages of an ID nodemoving through part of an exemplary transit path while associating withdifferent master nodes in accordance with an embodiment of theinvention;

FIG. 23 is a flow diagram illustrating an example method for associationmanagement of a wireless node network in accordance with an embodimentof the invention;

FIG. 24 is a flow diagram illustrating another example method forassociation management of a wireless node network in accordance with anembodiment of the invention;

FIG. 25 is a flow diagram illustrating yet another example method forassociation management of a wireless node network in accordance with anembodiment of the invention;

FIG. 26 is a flow diagram illustrating an exemplary method for contextmanagement of a wireless node network in accordance with an embodimentof the invention;

FIG. 27 is a flow diagram illustrating an exemplary method for locatinga node in a wireless node network based upon observed signal patternsand characteristic indications over a period of time in accordance withan embodiment of the invention;

FIG. 28 is a flow diagram illustrating an exemplary method for locationdetermination by varying a power characteristic of nodes in a wirelessnode network in accordance with an embodiment of the invention;

FIG. 29 is a flow diagram illustrating an exemplary method for locationdetermination using one or more associations of nodes in a wireless nodenetwork in accordance with an embodiment of the invention;

FIG. 30 is a flow diagram illustrating another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention;

FIG. 31 is a flow diagram illustrating yet another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention;

FIG. 32 is a flow diagram illustrating an exemplary method for locationdetermination of a first node in a wireless node network based oncontext data in accordance with an embodiment of the invention;

FIG. 33 is a flow diagram illustrating an exemplary method fordetermining a location using chaining triangulation for one of aplurality of nodes in a wireless node network having a server inaccordance with an embodiment of the invention;

FIGS. 34A-34D are diagrams illustrating various exemplary stages of anexample shipping and logistics operation using exemplary components of awireless node network in accordance with an embodiment of the invention;

FIG. 35 is a flow diagram illustrating an exemplary method forgenerating a shipping label for an item to be shipped using a wirelessnode network in accordance with an embodiment of the invention;

FIG. 36 is a flow diagram illustrating an exemplary method forconducting a payment transaction using a node association in a wirelessnode network in accordance with an embodiment of the invention;

FIG. 37 is a flow diagram illustrating an exemplary method for preparinga node-enabled shipment of an item to be shipped using a wireless nodenetwork in accordance with an embodiment of the invention;

FIG. 38 is a flow diagram illustrating an exemplary method for operationof a node-enabled logistics receptacle in a wireless node network inaccordance with an embodiment of the invention;

FIG. 39 is a flow diagram illustrating an exemplary method for shipmentmerging in a wireless node network in accordance with an embodiment ofthe invention;

FIG. 40 is a flow diagram illustrating another exemplary method forshipment merging in a wireless node network in accordance with anembodiment of the invention;

FIG. 41 is a flow diagram illustrating an exemplary method for deliverynotification using a wireless node network in accordance with anembodiment of the invention;

FIG. 42 is a diagram illustrating an example environment for picking upan order using exemplary components of a wireless node network inaccordance with an embodiment of the invention;

FIG. 43 is a flow diagram illustrating an exemplary method for pickingup an order using a wireless node network in accordance with anembodiment of the invention;

FIG. 44 is a flow diagram illustrating an exemplary method for managinga delivery of an item being shipped using a wireless node network inaccordance with an embodiment of the invention;

FIGS. 45A-45C are collectively a series of diagrams illustrating anexample environment where a node is located in and may move betweenareas having different operating node densities and adaptively adjustnode power in accordance with an embodiment of the invention;

FIG. 46 is a flow diagram illustrating an exemplary method for adaptiveadjustment of node power level in a wireless node network depending uponoperating node densities when a node moves to a new area in accordancewith an embodiment of the invention;

FIG. 47 is a flow diagram illustrating an exemplary method for adaptiveadjustment of node power level in a wireless node network depending upona threshold of operating nodes within a given area in accordance with anembodiment of the invention;

FIG. 48A-48C are diagrams illustrating various configurations of anexample wireless node network environment having an exemplarymagnetically actuated node in accordance with an embodiment of theinvention;

FIG. 49A-49B are diagrams illustrating an example wireless node networkenvironment having an exemplary magnetically actuated node and anexemplary magnetic placement support in accordance with an embodiment ofthe invention;

FIG. 50A-50B are diagrams illustrating an example wireless node networkenvironment having an exemplary magnetically actuated node integratedinto an exemplary placement support for a moveable magnetic object inaccordance with an embodiment of the invention;

FIG. 51 is a flow diagram illustrating an exemplary method formagnetically altering an operation of a node in a wireless node networkhaving a master node and a server in accordance with an embodiment ofthe invention;

FIG. 52 is a flow diagram illustrating an exemplary method for adjustinga broadcast setting of a node in a wireless node network having a masternode and a server in accordance with an embodiment of the invention;

FIG. 53 is a flow diagram illustrating an exemplary method for enhancedpower notification from an ID node in a wireless node network having amaster node and a server in accordance with an embodiment of theinvention;

FIG. 54 is a diagram illustrating an exemplary coupler connectionbetween two conveyance systems having an integrated node in accordancewith an embodiment of the invention;

FIG. 55 is a more detailed diagram illustrating the exemplary couplerconnector between two systems having an integrated node in accordancewith an embodiment of the invention;

FIG. 56 is a diagram illustrating another exemplary coupler connectionbetween two conveyance systems having an adapter node in accordance withan embodiment of the invention;

FIG. 57 is a flow diagram illustrating an exemplary method formonitoring at least one signal passing through a coupling connectionhaving a network device that communicates on a wireless node network inaccordance with an embodiment of the invention;

FIG. 58 is a flow diagram illustrating an exemplary method for sharingshipment condition information in a wireless node network having aplurality of network devices and a server in accordance with anembodiment of the invention;

FIG. 59 is a flow diagram illustrating an exemplary method forrequesting shared shipment condition information in a wireless nodenetwork having a plurality of network devices and a server in accordancewith an embodiment of the invention;

FIG. 60A is a diagram illustrating an exemplary group of nodesassociated with a multi-piece shipment in an exemplary shippingcontainer in accordance with an embodiment of the invention;

FIG. 60B is a diagram illustrating an exemplary group of nodesassociated with a multi-piece shipment on an exemplary shipping palletin accordance with an embodiment of the invention;

FIG. 61 is a flow diagram illustrating an exemplary method of serveroperations when creating a hierarchical sensor network for a grouped setof packages being shipped in accordance with an embodiment of theinvention;

FIG. 62 is a flow diagram illustrating an exemplary method of masternode operations when creating a hierarchical sensor network for agrouped set of packages being shipped in accordance with an embodimentof the invention;

FIG. 63 is a flow diagram illustrating an exemplary method of creating ahierarchical sensor network for a grouped set of packages being shippedin accordance with an embodiment of the invention;

FIG. 64 is a flow diagram illustrating an exemplary method formulti-entity management of an ID node in a wireless node network inaccordance with an embodiment of the invention;

FIG. 65 is a flow diagram illustrating an exemplary method formulti-entity management of an ID node in a wireless node network fromthe perspective of a shipping customer entity in accordance with anembodiment of the invention;

FIG. 66 is a flow diagram illustrating an exemplary method formulti-entity management of an ID node in a wireless node network fromthe perspective of recipient entity in accordance with an embodiment ofthe invention;

FIGS. 67A-67D are diagrams illustrating an exemplary node-enabledautonomous transport vehicle in various stages of navigating using nodesin a wireless node network in accordance with an embodiment of theinvention;

FIG. 68 is a flow diagram illustrating an exemplary method fornavigating to a shipping location by an autonomous transport vehicleusing a plurality of nodes in a wireless node network in accordance withan embodiment of the invention;

FIG. 69A is a diagram illustrating an exemplary courier transportvehicle having an exemplary node-enabled autonomous vehicle inaccordance with an embodiment of the invention;

FIG. 69B is a diagram illustrating the exemplary node-enabled autonomousvehicle as it approaches a package and related ID node for an exemplarylogistics transaction at a transaction location in accordance with anembodiment of the invention;

FIG. 70 is a flow diagram illustrating an exemplary method forautomating a logistics transaction using a plurality of nodes and aserver in a wireless node network in accordance with an embodiment ofthe invention;

FIG. 71 is a diagram illustrating an exemplary hierarchical node networkfor monitoring a piece of equipment within an exemplary healthcarefacility in accordance with an embodiment of the invention;

FIG. 72 is a flow diagram illustrating an exemplary method formonitoring a piece of equipment using a hierarchical node network havingat least an ID node, a master node, and a server in accordance with anembodiment of the invention;

FIG. 73 is a flow diagram illustrating an exemplary method formonitoring a person's activity using a hierarchical node network havingat least an ID node, a master node, and a server in accordance with anembodiment of the invention;

FIG. 74 is a flow diagram illustrating an exemplary method forinitiating a pre-staged preparation related to medical treatment to beprovided to a patient at a healthcare facility using a hierarchical nodenetwork in accordance with an embodiment of the invention;

FIG. 75A is a diagram illustrating an exemplary container usingnode-enabled packaging material as part of an exemplary wireless nodenetwork in accordance with an embodiment of the invention;

FIG. 75B is a diagram illustrating another exemplary container usingnode-enabled packaging material as part of an exemplary wireless nodenetwork in accordance with an embodiment of the invention;

FIG. 76 is a diagram illustrating a view of an exemplary container sheetusing node-enabled packaging material as part of an exemplary wirelessnode network in accordance with an embodiment of the invention;

FIG. 77 is a diagram illustrating a perspective view of an exemplaryassembled container using node-enabled packaging material as part of anexemplary wireless node network in accordance with an embodiment of theinvention;

FIG. 78 is a diagram illustrating a perspective view of exemplarynode-enabled packaging material implemented with exemplary packagingseparator sheet material and exemplary cushioning material in accordancewith an embodiment of the invention;

FIG. 79 is a flow diagram illustrating an exemplary method usingnode-enabled packaging material as part of a container for an item to beshipped in accordance with an embodiment of the invention;

FIG. 80 is a diagram illustrating an exemplary user access device andpackage approaching an exemplary shipping facility where an exemplarysystem notifies a shipping customer about an alternative shippingsolution in accordance with an embodiment of the invention;

FIG. 81 is a flow diagram illustrating an exemplary method forproactively notifying a shipping customer using a wireless node networkabout an alternative shipping solution when shipping a package inaccordance with an embodiment of the invention;

FIG. 82A is a perspective diagram illustrating an exterior view of anexemplary node-enabled logistics receptacle in accordance with anembodiment of the invention;

FIG. 82B is a diagram illustrating a side and internal view into theexemplary node-enabled logistics receptacle of FIG. 82A in accordancewith an embodiment of the invention;

FIG. 83 is a diagram illustrating an exemplary node-enabled logisticsreceptacle that can assess the suitability of a current location of theexemplary node-enabled logistics receptacle in accordance with anembodiment of the invention;

FIG. 84 is a flow diagram illustrating an exemplary method for assessinga current location for a node-enabled logistics receptacle in accordancewith an embodiment of the invention;

FIG. 85A is a diagram illustrating an exemplary node-enabled logisticsreceptacle with a master node assembled within the logistics receptacleand ready to receive a package in accordance with an embodiment of theinvention;

FIG. 85B is a diagram illustrating the exemplary node-enabled logisticsreceptacle with the master node assembled within the logisticsreceptacle of FIG. 85A with the package within the node-enabledlogistics receptacle in accordance with an embodiment of the invention;

FIG. 86A is a diagram illustrating an exemplary node-enabled logisticsreceptacle with an ID node assembled within the logistics receptacle andready to receive a package in accordance with an embodiment of theinvention;

FIG. 86B is a diagram illustrating the exemplary node-enabled logisticsreceptacle with the ID node assembled within the logistics receptacle ofFIG. 86A with the package within the node-enabled logistics receptaclein accordance with an embodiment of the invention;

FIG. 87 is a flow diagram illustrating an exemplary method forproactively reporting a content status of a node-enabled logisticsreceptacle in a wireless node network in accordance with an embodimentof the invention;

FIG. 88 is a flow diagram illustrating another exemplary method forproactively reporting a content status of a node-enabled logisticsreceptacle in a wireless node network in accordance with an embodimentof the invention;

FIG. 89A is a diagram illustrating an exemplary node-enabled logisticsreceptacle with a node and an exemplary sensor assembled within thelogistics receptacle in accordance with an embodiment of the invention;

FIG. 89B is a diagram illustrating an exemplary node-enabled logisticsreceptacle with a node and another type of exemplary sensor assembledwithin the logistics receptacle in accordance with an embodiment of theinvention;

FIG. 89C is a diagram illustrating another exemplary node-enabledlogistics receptacle with a node and still other types of exemplarysensors used as part of the node-enabled logistics receptacle inaccordance with an embodiment of the invention;

FIG. 89D is a diagram illustrating still another exemplary node-enabledlogistics receptacle with a node and further other types of exemplarysensors used as part of the node-enabled logistics receptacle inaccordance with an embodiment of the invention;

FIG. 90 is a flow diagram illustrating an exemplary method for detectinga plurality of package types within a node-enabled logistics receptaclein a wireless node network in accordance with an embodiment of theinvention;

FIG. 91 is a diagram illustrating an exemplary node-enabled logisticsreceptacle that reports a current status of packages to a server forenhanced deployment of pickup services by pickup entities in accordancewith an embodiment of the invention;

FIG. 92 is a flow diagram illustrating an exemplary method deploying aplurality of pickup entities to a node-enabled logistics receptacle in awireless node network in accordance with an embodiment of the invention;

FIG. 93 is a diagram illustrating exemplary node packages located in anexemplary vehicle environment in accordance with an embodiment of theinvention;

FIG. 94 is a diagram illustrating exemplary mobile storage units, suchas ULDs, used as containers that help ship node packages in an exemplaryairborne environment in accordance with an embodiment of the invention;

FIG. 95 is a diagram illustrating an exemplary ID node device adapted tooperate in a pseudo master node mode in accordance with an embodiment ofthe invention;

FIG. 96 is a diagram illustrating an exemplary hierarchical wirelessnode network in accordance with an embodiment of the invention;

FIG. 97 is a flow diagram illustrating an exemplary method for nodecommunication within a hierarchical wireless node network in accordancewith an embodiment of the invention;

FIGS. 98A-98C are a series of diagrams illustrating variousconfigurations of an exemplary node as it adaptively alters how itformats a broadcasted advertising message in response to detected statechanges for the node in accordance with an embodiment of the invention;

FIG. 99 is a flow diagram illustrating an exemplary method for adaptivenode communication within a wireless node network having a plurality ofnodes in accordance with an embodiment of the invention;

FIG. 100 is a flow diagram illustrating an exemplary method for adaptivenode communication within a wireless node network having at least amaster node and an ID node in accordance with an embodiment of theinvention;

FIGS. 101A-101B are diagrams illustrating different points in time foran exemplary delivery notification stage involving an exemplary mobiledelivery point in accordance with an embodiment of the invention;

FIG. 102 is a flow diagram illustrating an exemplary method for deliveryto a mobile delivery point and notification of an intended recipient inaccordance with an embodiment of the invention; and

FIG. 103 is a flow diagram illustrating an exemplary method for deliveryto a mobile delivery point and notification of an identified entity inaccordance with an embodiment of the invention.

DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to exemplary embodiments. Whereverpossible, the same reference numbers are used in the drawings and thedescription to refer to the same or like parts.

In general, the following describes various embodiments of acontextually aware hierarchical wireless node network that may bemanaged, operated, and applied by principles as set forth herein. Ingeneral, embodiments of the wireless node network may include one ormore lower level devices or nodes (e.g., an ID node) that rely onshorter-range communication with a higher level device or node (e.g., amaster node), which is operative to communicate with a server over adifferent communication interface while the lower level node is unableto communicate directly with the server. Those skilled in the art willappreciate that such a hierarchy of different functional communicatingnetwork components (generally referred to as network devices) may becharacterized as a network of nodes. Those skilled in the art willappreciate that in some embodiments, the wireless node network mayinclude the server as well as different wireless nodes despite the factthat the server may not be a dedicated wireless component. In otherembodiments, the network may include similar types of wireless nodes ordifferent types of wireless nodes.

Further, those skilled in the art will appreciate that each embodimentdescribed herein effects improvements to particular technologies, suchas asset identification and monitoring, location services, logisticsoperations & infrastructure, and node operation and management using anadaptive, context-aware wireless node network. Each embodiment describesa specific technological application of one or more nodes that operatein such a wireless node network where the specific technologicalapplication improves or otherwise enhances such technical fields asexplained and supported by the disclosure that follows.

Those skilled in the art will understand through the following detaileddescription that the nodes may be associated with items (e.g., anobject, a package, a person, a piece of equipment) and may be used toidentify and locate the items while being dynamically programmed duringoperation of the network and while the items move along an anticipatedpath (e.g., a transit path from an origin point to a destination point).The following further describes various embodiments of a wireless nodenetwork, exemplary ways to manage components of a wireless node network,exemplary ways to better determine the location of components of awireless node network, and applications of a wireless node network toenhance logistics operations that rely upon a wireless node network.

Wireless Node Networks

FIG. 1 illustrates a basic diagram of an exemplary wireless node networkin accordance with an embodiment of the invention. The exemplary networkshown in FIG. 1 comprises a server 100 connected to a network 105, whichis also operatively connected to different network components, such as amaster node 110 a and indirectly to an ID node 120 a through master node110 a. Master node 110 a is typically connected to an ID node 120 a viashort-range wireless communications (e.g., Bluetooth® formattedcommunications). Master node 110 a is typically connected to server 100through network 105 via longer-range wireless communication (e.g.,cellular) and/or medium range wireless communication (e.g., wirelesslocal area data networks or Wi-Fi). ID node 120 a is typically a lowcost device that may be easily placed into a package, be integrated aspart of packaging, or otherwise associated with an item to be trackedand located, such as package 130, a person, or object (e.g., vehicle,etc.). Generally, an ID node is capable of communicating directly with amaster node but incapable of communicating directly with the server,while a master node is capable of communicating directly with the serverand separately and directly communicating with other nodes (such as anID node or another master node). The ability to deploy a hierarchy ofnodes within an exemplary wireless node network to distribute tasks andfunctions at the different levels in an efficient and economical mannerhelps to facilitate a wide variety of adaptive locating, tracking,managing, and reporting applications using such a network of nodes asdiscussed in more detail below.

In general, the lower cost, lower complexity ID node 120 a is managed bythe higher complexity master node 110 a and server 100 as part ofkeeping track of the location of ID node 120 a (and the associateditem), thereby providing intelligent, robust, and broad visibility aboutthe location and status of ID node 120 a. In a typical embodiment, IDnode 120 a is first associated with an item (e.g., package 130, aperson, or object). As ID node 120 a moves with the item, the ID node120 a becomes associated with the master node 110 a, and the server 100is updated with such information. Further movement of the ID node 120 aand item may cause the ID node 120 a to disassociate with master node110 a and be handed off to become associated another master node (notshown), after which the server 100 is again updated. As such, the server100 generally operates to coordinate and manage information related tothe ID node 120 a as the item physically moves from one location toanother. Further details of the architecture and functionality of anembodiment of an exemplary ID node and master node as described below inmore detail with respect to FIGS. 3 and 4, while exemplary server 100 isdescribed below in more detail with respect to FIG. 5.

While server 100 is shown connecting through network 105, those skilledin the art will appreciate that server 100 may have a more direct ordedicated connections to other components illustrated in FIG. 1, such asmaster node 110 a, depending upon implementation details and desiredcommunication paths. Furthermore, those skilled in the art willappreciate that an exemplary server may contain a collection ofinformation in a database (not shown in FIG. 1), while multipledatabases maintained on multiple server platforms or network storageservers may be used in other embodiments to maintain such a collectionof information. Furthermore, those skilled in the art will appreciatethat a database may be implemented with cloud technology thatessentially provides networked storage of collections of informationthat may be directly accessible to devices, such as master node 110 a.

Network 105 may be a general data communication network involving avariety of communication networks or paths. Those skilled in the artwill appreciate that such exemplary networks or paths may be implementedwith hard wired structures (e.g., LAN, WAN, telecommunication lines,telecommunication support structures and telecommunication processingequipment, etc.), wireless structures (e.g., antennas, receivers,modems, routers, repeaters, etc.) and/or a combination of both dependingupon the desired implementation of a network that interconnects server100 and other components shown in FIG. 1 in an embodiment of the presentinvention.

Master node 110 a and ID node 120 a are types of nodes. A node isgenerally an apparatus or device used to perform one or more tasks aspart of a network of components. An embodiment of a node may have aunique identifier, such as a Media Access Control (MAC) address or anaddress assigned to a hardware radio like an Internet Protocol 6 (IPv6)identifier. In some embodiments, the node's unique identifier may becorrelated to a shipment identifier (e.g., a shipment tracking number inone example), or may itself be a shipment's tracking reference.

An ID node, such as ID node 120 a, is generally a low cost activewireless device. In one embodiment, an exemplary ID node is atransceiver-based processing or logic unit having a short-range radiowith variable RF characteristics (e.g., programmable RF output powerrange, programmable receiver sensitivity), memory accessible by theprocessing unit, a timer operatively coupled to the processing unit, anda power source (e.g., a battery) that provides power for the circuitryof the ID node. For example, the physical implementation of an exemplaryID node may be small, and, thus, amenable to integration into a package,label, container, or other type of object. In some implementations of anID node, the node is rechargeable while other implementations do notpermit recharging the power source for the ID node. In otherimplementations, the ID node is environmentally self-contained or sealedso as to enable robust and reliable operations in a variety ofenvironmentally harsh conditions.

A master node, such as master node 110 a, generally serves as anintelligent bridge between the ID node 120 a and the server 100.Accordingly, a master node is generally more sophisticated than an IDnode. In one example embodiment, an exemplary master node is a devicehaving a processing or logic unit, a short-range radio (with may havevariable RF characteristics) used for communicating with other nodes (IDnodes and other master nodes), a medium and/or long-range radio forcommunication with the server 100, memory accessible by the processingunit, a timer operatively coupled to the processing unit, and a powersource (e.g., a battery or a wired power supply connection) thatprovides power for the circuitry of the master node. The exemplarymaster node, such as master node 110 a, may be positioned in a knownfixed location or, alternatively, be a mobile unit having dedicatedlocation positioning circuitry (e.g., GPS circuitry) to allow the masternode to determine its location by itself.

While the embodiment illustrated in FIG. 1 shows only a single masternode and a single ID node, those skilled in the art will appreciate thata wireless network consistent with an embodiment of the invention mayinclude a wide array of similar or different master nodes that eachcommunicate with the server 100 and/or other master nodes, and a widevariety of similar or different ID nodes. Thus, the exemplary networkshown in FIG. 1 is a basic embodiment, while the exemplary network shownin FIG. 2 is a more detailed exemplary wireless node network inaccordance with another embodiment of the invention

Referring now to FIG. 2, another exemplary wireless node network isshown including server 100 and network 105. Here, master nodes 110 a,110 b, 110 c are deployed and connected to network 105 (and by virtue ofthose respective connections, to server 100) as well as to each other.ID nodes 120 a, 120 b, 120 e are shown as connectable or operative tocommunicate via different paths to various master nodes. However, IDnodes 120 c and 120 d are shown in FIG. 2 connected to ID node 120 b butnot to any of the master nodes. This may be the case if, for example, IDnodes 120 b, 120 c, 120 d are associated with different items (e.g.,packages) within a larger container 210 (or grouped together on apallet). In such an example, only ID node 120 b may remain within thewireless communication range of any master node. This may, for example,be because of the positions of the different ID nodes within thecontainer relative to the closest master node, adverse RF shieldingcaused by the container, adverse RF shielding caused by packaging of theitem, or adverse RF shielding caused by other proximate material thatinterferes with radio transmissions (e.g., several packages of metalitems between the ID node and any master node outside the container).Thus, in the illustrated configuration of the exemplary network shown inFIG. 2, ID nodes 120 c and 120 d may be out of range from the masternodes, yet still have an operative communication path to a master nodethrough ID node 120 b.

Indeed, in one example, prior to placement within container 210, ID node120 b may actually be a master node but the changed RF environment whenplacing it in container 210 may interfere with the master node's abilityto locate itself via location signals (e.g., GPS signals) and cause themaster node to temporarily operate as an ID node while still providingcommunications and data sharing with other ID nodes in container 210.

User access devices 200, 205 are also illustrated in FIG. 2 as beingable to connect to network 105, master nodes, and ID nodes. Generally,user access devices 200 and 205 allow a user to interact with one ormore components of the exemplary wireless node network. In variousembodiments, user access devices 200, 205, may be implemented using adesktop computer, a laptop computer, a tablet (such as an Apple iPad®touchscreen tablet), a personal area network device (such as aBluetooth® device), a smartphone (such as an Apple iPhone®), a smartwearable device (such as a Samsung Galaxy Gear™ smartwatch device, or aGoogle Glass™ wearable smart optics) or other such devices capable ofcommunicating over network 105 with server 100, over a wired or wirelesscommunication path to master node and ID nodes.

As shown in FIG. 2, user access devices 200, 205 are coupled and incommunication with network 105, but each of them may also be incommunication with each other or other network components in a moredirect manner (e.g., via near field communication (NFC), over aBluetooth® wireless connection, over a WiFi network, dedicated wiredconnection, or other communication path).

In one example, a user access device, such as device 200 or 205, mayfacilitate associating an ID node (such as ID node 120 a) with thetracking number of a package at the start of a shipment process,coordinating with the server 100 to check on the status and/or locationof the package and associated ID node during transit, and possiblyretrieving data from a master node or ID node related to the shippedpackage. Thus, those skilled in the art will appreciate that a useraccess device, such as devices 200, 205, are essentially interactivecommunication platforms by which a user may initiate shipment of anitem, track an item, determine the status and location of an item, andretrieve information about an item.

An exemplary user access device, such as device 200 or 205, may includesufficient hardware and code (e.g., an app or other program code sectionor sections) to operate as a master node or an ID node in variousembodiments as discussed in more detail below. For example, device 200may be implemented as a mobile smartphone and functionally may operateas an exemplary ID node that broadcasts advertising packet messages toother ID nodes or master nodes for association and sharing data withsuch nodes. In another example, device 200 is implemented as a mobilesmartphone and may operate as an exemplary master node that communicatesand associates with ID nodes and other master nodes, as describedherein, and communicates with the server 100. Thus, those skilled in theart will appreciate an exemplary ID node in FIG. 3 and an exemplarymaster node in FIG. 4, and their respective parts, code and programmodules, may be implemented with an appropriately programmed user accessdevice, such as device 200 or 205. Thus, the following description of anexemplary ID node in FIG. 3 and an exemplary master node in FIG. 4 willbe applicable to a user access device operating as an ID node or amaster node, respectively.

ID Node

FIG. 3 is a more detailed diagram of an exemplary ID node device inaccordance with an embodiment of the invention. As previously described,one embodiment of an ID node includes a transceiver-based processing orlogic unit having a short-range radio with variable RF characteristics(e.g., programmable RF output power range, programmable receiversensitivity), memory accessible by the processing unit, a timeroperatively coupled to the processing unit, and a power source (e.g., abattery) that provides power for the circuitry of the ID node. Referringnow to the more detailed embodiment of FIG. 3, exemplary ID node 120 ais shown to comprise a processing or logic unit 300 coupled to avariable power short-range communication interface 375, memory storage315, volatile memory 320, timer 370, and battery 355. Those skilled inthe art will appreciate that processing unit 300 is logic, such as a lowpower consumption microcontroller, that generally performs computationson data and executes operational and application program code and otherprogram modules or sections thereof within the ID node 120 a. As such,exemplary processing unit 300 operates as a transceiver-based processingcore of ID node 120 a.

Those skilled in the art will also appreciate that exemplary ID node 120a is a hardware-based component that may be implemented with a singleprocessor or logic unit, such as unit 300. In one embodiment, processingunit 300 may be implemented with an Intel® 8051 CPU Core and associatedperipheral circuitry as dictated by the needs of the particularapplication. Less complex microcontrollers or discrete circuitry may beused to implement processing unit 300 as well as more complex andsophisticated microprocessors. Additionally, exemplary processing unit300 may be integrated into a single chip transceiver used as a core ofID node 120 a.

The variable power short-range communication interface 375 of ID node120 a is generally a programmable radio and an omni-directional antennacoupled to the processing unit 300. In other embodiments, interface 375may use an antenna with a different antenna profile when directionalitymay be desired. Examples of variable power short-range communicationinterface 375 may include other interfacing hardware (not shown) foroperatively coupling the device to a specific short-range communicationpath (e.g., a Bluetooth® Low Energy (BLE) connection path communicatingat 2.4 GHz).

In one embodiment, various RF characteristics of the radio'stransceiver, such as the RF output power and/or the RF receiversensitivity may be dynamically and programmatically varied under controlof processing unit 300. In other embodiments, further RF characteristicsof the radio's transceiver may be programmatically varied, such asfrequency, duty cycle, timing, modulation schemes, spread spectrumfrequency hopping aspects, etc., as needed to flexibly adjust the RFoutput signal depending upon a desired implementation and anticipateduse of ID node 120 a. As will be explained in more detail below, someembodiments may use Broadcast Profile having parameters that may beprogrammatically altered or adjusted. In other words, embodiments of IDnode 120 a (or any other ID node) may have programmatically adjustableRF characteristics (such as an adjustable RF output signal power, anadjustable RF receiver sensitivity, the ability to switch to a differentfrequency or frequency band, etc.).

The battery 355 for ID node 120 a is a type of power source thatgenerally powers the circuitry implementing ID node 120 a. In oneembodiment, battery 355 may be a rechargeable power source. In otherembodiments, battery 355 may be a non-rechargeable power source intendedto be disposed of after use. In some embodiments of an ID node, thepower source may involve alternative energy generation, such as a solarcell.

The timer 370 for ID node 120 a generally provides one or more timingcircuits used in, for example, time delay, pulse generation, andoscillator applications. In an embodiment where ID node 120 a conservespower by entering a sleep or dormant state for a predetermined timeperiod as part of overall power conservation techniques, timer 370assists processing unit 300 in managing timing operations. Additionally,an embodiment may allow an ID node to share data to synchronizedifferent nodes with respect to timer 370 and a common timing referencebetween nodes and the server.

An embodiment may implement ID node 120 a to optionally include a basicuser interface (UI) 305 indicating status and allowing basic interactionlike start/stop. In one embodiment, the UI 305 may be implemented withstatus lights, such as multi-mode LEDs. Different colors of the lightsmay indicate a different status or mode for the ID node 120 a (e.g., anadvertising mode (broadcasting), a scanning mode (listening), a currentpower status, a battery level status, an association status, an error,as sensed condition (e.g., exceeding a temperature threshold, exceedinga moisture threshold, and the like)). Other embodiments of an ID nodemay implement U! 305 in a more sophisticated manner with a graphicsdisplay or the like where such status or mode information may bedisplayed as well as one or more prompts.

In a further embodiment, an exemplary status light used as part of theUI 305 of an ID node may also indicate a shipment state. In more detail,an exemplary shipment state may include a status of the shipped item ora status of the item's current shipment journey from an origin to adestination.

An embodiment may also implement ID node 120 a to optionally include oneor more sensors 360. In some embodiments, an ID node implemented withone or more sensors 360 may be referred to as a Sensor node. Examples ofsensor 360 may include one or more environmental sensors (e.g.,pressure, movement, light, temperature, humidity, magnetic field,altitude, attitude, orientation, acceleration, etc.) and dedicatedlocation sensors (e.g., GPS sensor, IR sensor, proximity sensor, etc.).Those skilled in the art will understand that additional types ofsensors that measure other characteristics are contemplated for use assensor 360. Additionally, those skilled in the art will understand thata Sensor node may include additional program features to manage thecollection, storage, sharing, and publication of the captured sensordata.

An embodiment may further implement ID node 120 a to optionally includeone or more magnetic switches 365. A magnetic switch 365, such as a reedswitch, generally operates to close or open an electrical path orconnection in response to an applied magnetic field. In other words,magnetic switch 365 is actuated by the presence of a magnetic field orthe removal of a magnetic field. Various applications, as discussed inembodiments described in more detail below, may involve the operation ofID node 120 a having magnetic switch 365.

Consistent with the embodiment shown in FIG. 3, exemplary ID node 120 amay be implemented based upon a Texas Instruments CC2540 Bluetooth® LowEnergy (BLE) System-on-Chip, which includes various peripherals (e.g.,timer circuitry, USB, USART, general-purpose I/O pins, IR interfacecircuitry, DMA circuitry) to operate as an ID node and, if necessary, tointerface with different possible sensors and other circuitry (e.g.,additional logic chips, relays, magnetic switches) that make up the IDnode.

In additional embodiments, one skilled in the art will appreciate thatsimilar functionality in an ID node may be implemented in other types ofhardware. For example, ID node 110 a may be implemented with speciallyoptimized hardware (e.g., a particular application specific integratedcircuit (ASIC) having the same operational control and functionality asnode control and management code, as described below, discrete logic, ora combination of hardware and firmware depending upon requirements ofthe ID node, such as power, processing speed, level of adjustability forthe RF characteristics, number of memory storage units coupled to theprocessor(s), cost, space, etc.

As noted above, ID node 120 a includes memory accessible by theprocessing unit 300. Memory storage 315 and volatile memory 320 are eachoperatively coupled to processing unit 300. Both memory componentsprovide programming and data elements used by processing unit 300. Inthe embodiment shown in FIG. 3, memory storage 315 maintains a varietyof program code (e.g., node control and management code 325) and otherdata elements (e.g., profile data 330, security data 335, associationdata 340, shared data 345, sensor data 350, and the like). Memorystorage 315 is a tangible, non-transient computer readable medium onwhich information (e.g., executable code/modules, node data, sensormeasurements, etc.) may be kept in a non-volatile and non-transitorymanner. Examples of such memory storage 315 may include a hard diskdrive, ROM, flash memory, or other media structure that allows longterm, non-volatile storage of information. In contrast, volatile memory320 is typically a random access memory (RAM) structure used byprocessing unit 300 during operation of the ID node 120 a. Upon power upof ID node 120 a, volatile memory 320 may be populated with anoperational program (such as node control and management code 325) orspecific program modules that help facilitate particular operations ofID node 120 a. And during operation of ID node 120 a, volatile memory320 may also include certain data (e.g., profile data 330, security data335, association data 340, shared data 345, sensor data 350, and thelike) generated as the ID node 120 a executes instructions as programmedor loaded from memory storage 315. However, those skilled in the artwill appreciate that not all data elements illustrated in FIG. 3 mustappear in memory storage 315 and volatile memory 320 at the same time.

Node Control & Management Code

Generally, an embodiment of node control and management code 325 is acollection of software features implemented as programmatic functions orprogram modules that generally control the behavior of a node, such asID node 120 a. In an embodiment, the functionality of code 325 may begenerally similar as implemented in different types of nodes, such as amaster node, an ID node, and a sensor node. However, those skilled inthe art will appreciate that while some principles of operation aresimilar between such nodes, other embodiments may implement thefunctionality with some degree of specialization or in a differentmanner depending on the desired application and use of the node.

In a general embodiment, exemplary node control and management code 325may generally comprise several programmatic functions or program modulesincluding (1) a node advertise and query (scan) logic manager (alsoreferred to herein as a node communications manager), which manages howand when a node communicates; (2) an information control and exchangemanager, which manages whether and how information may be exchangedbetween nodes; (3) a node power manager, which manages power consumptionand aspects of RF output signal power and/or receiver sensitivity forvariable short-range communications; and (4) an association managerfocusing on how the node associates with other nodes. What follows isdescription of various embodiments of these basic program modules usedby nodes.

Node Communications Manager—Advertising & Scanning

In an exemplary embodiment, the node advertise and query (scan) logicmanager governs how and when a node should advertise (transmit) itsaddress or query (scan) for the address of neighboring nodes.Advertising is generally done with a message, which may have differentinformation in various parts (e.g., headers, fields, flags, etc.). Themessage may be a single or multiple packets.

In the exemplary embodiment, the “advertise” mode (as opposed to “query”or “scan” mode) is a default mode for an ID Node and has the nodebroadcasting or transmitting a message with its address and relatedmetadata regarding the node. For example, in one embodiment, exemplarymetadata may include information such as the RF output power level, areference number, a status flag, a battery level, and a manufacturername for the node.

FIG. 6 is a diagram illustrating the structure or format of an exemplaryadvertisement data packet in accordance with a general embodiment of theinvention. Referring now to FIG. 6, the structure of an exemplaryadvertisement data packet 600 broadcast as a signal or message from anID node, such as ID node 120 a, is shown. Packet 600 appears with anincreasing level of detail showing exemplary metadata and a format thatseparately maintains distinct types of metadata in different parts ofthe packet. Different embodiments may include different types ofmetadata depending on the deployed application of the ID node.

FIG. 7 is a diagram illustrating sample content for an exemplaryadvertisement data packet in accordance with an embodiment of theinvention. Referring now to FIG. 7, an exemplary advertisement datapacket 700 is illustrated with exemplary metadata including showingsample information such as the RF Output Power level (e.g., “TX PowerLevel”), a reference number (e.g., “‘FDX ID’ (ASCII Short Name)”, astatus flag (e.g., “Status Flag Value (indicates ‘Ack Requested’)”), abattery level (e.g., “Battery Level Value (Indicates 73% charge)”, and amanufacturer name for the node (e.g., “Company Identifier (currentlyundefined for FedEx)”). In one embodiment, those skilled in the art willappreciate that the reference number may be omitted or obfuscated forsecurity purposes.

In one embodiment, an exemplary advertising data packet may include theRF Output power level, as noted above in FIG. 7, to enable one way tohelp identify the type of node doing the broadcasting and the locationof the broadcasting node. However, if the broadcast RF output powerlevel is fixed and known by the node type, only the node type need beidentifiable from an exemplary advertising data packet, such as packet700.

Regarding how a node communicates, an exemplary node may be in one ofseveral different communication modes. A node in an advertising (ortransmit or broadcast) mode is visible to any other node set in a query(or scan or listen) mode. In an embodiment, the frequency and length ofadvertising may be application and power dependent. For example, innormal operations, an exemplary node will generally advertise in aperiodic manner and expect to make an active connection to another nodeat certain intervals, which may be dictated by conditions set by server100. In an embodiment, such conditions may be set individually for anode by the server or a higher level node in the network.

If an exemplary node has not received acknowledgement for an advertisingpacket within a particular period, it may enter one or more alertstages. For example, if an exemplary node has not receivedacknowledgement from another node for an advertising packet broadcast bythe exemplary node within a particular time period (also generallyreferred to as an Alert Interval), the exemplary node will enter anAlert Stage 1 status. This prompts the exemplary node to issue afollow-up advertising packet having one or more parts of it altered toindicate the Alert Stage 1 status. In more detail, this exemplaryfollow-up advertising packet may have a different advertising alertheader instructing nearby nodes to send a SCAN_REQ message uponreceiving an advertisement packet.

If an exemplary node has not received acknowledgement from a master nodefor an advertising packet broadcast by the exemplary node within anothertime period (e.g., a request from the master node to actively connectand a success connection made), it will enter another alert stage, suchas an Alert Stage 2 status. This prompts the exemplary node to issue afollow-up advertising packet having one or more parts of it altered toindicate the Alert Stage 2 status. In more detail, this exemplaryfollow-up advertising packet may have a different advertising alertheader instructing nearby master nodes to send a SCAN_REQ message uponreceiving an advertisement packet.

If an exemplary node has data to upload to the backend, it may alsoenter another type of alert stage. In one embodiment, for example, if anexemplary node has sensor data collected by the exemplary node (orreceived from one or more other nodes that have communicated with theexemplary node), and the data needs to be uploaded to server 100, theexemplary node may enter an update alert stage, such as an Alert Stage3. This prompts the exemplary node to issue a follow-up advertisingpacket having one or more parts of it altered to indicate the AlertStage 3 status. In more detail, this exemplary follow-up advertisingpacket may have a different advertising alert header instructing nearbymaster nodes to make a connection with the exemplary node so that thedata (e.g., sensor data 350) may be transmitted from the exemplary node(e.g., ID node 120 a) to a nearby master node (e.g., master node 110 a).The transmitted data may then be stored by the nearby master node assensor data 450 in either or both of the master node's volatile memory420 and memory storage 415. Subsequent to that storage operation, thenearby master node will transfer the data (e.g., sensor data 450) toserver 100.

As illustrated in FIG. 7 and explained in the above description of alertlevel stages, a status flag in a header of an exemplary advertising datapacket is a field used in the association logic in one or moreembodiments. For example, in one embodiment, the existence of a statusflag in the advertising data packet allows a first node to communicateits status to a second node, and for the second node to report thatstatus to the backend server, such as server 100, without an activedirect connection from the first node to the server. In other words, thestatus flag helps facilitate passive interactions between nodes (such aspassive associations).

In a more detailed embodiment, several exemplary status types areestablished with respect to communications with other nodes. Forexample, the exemplary status types may comprise the following:

-   -   Alert Level 0—no issue, operating normal;    -   Alert Level 1—The advertising node is requesting that any        available node acknowledge the receipt of its advertisement        packet;    -   Alert Level 2—The advertising node is requesting that any        available master node acknowledge the receipt of its        advertisement packet;    -   Alert Level 3—Data for Upload—node has captured data available        for upload through a master node; and    -   Synchronize—The advertising node requests to connect with a        device or sensor that can synchronize data (such as timer or        location information).

By broadcasting the status via, for example, a portion of a header in anadvertising data packet, one or more nodes within range of thebroadcasting node can determine the node's status and initiate activeconnections if requested in the status message.

A request for more information from the advertising node may, in someembodiments, come in the form of a SCAN_REQ message. In general, anexemplary SCAN_REQ is a message sent from a scanning (listening) masternode to an advertising node requesting additional information from theadvertising node. In this example, the alert status bit may indicate tothe scanning master node, for example, at an application layer, whetherthe advertising node is in a mode that will or will not accept aSCAN_REQ. In one embodiment, the non-connectable and discoverable modesof node advertising are in compliance with Bluetooth® Low Energy (BLE)standards.

In another embodiment, a node may have further different modes ofoperation while scanning or listening for other nodes. For example, anode's query or scanning mode may be active or passive. When a node isscanning while passive, the node will receive advertising data packets,but will not acknowledge and send SCAN_REQ. However, when a node isscanning while active, the node will receive advertising data packets,and will acknowledge receipt by sending a SCAN_REQ. A more detailedembodiment may provide the passive and active modes of scanning orinquiry in compliance with Bluetooth® Low Energy (BLE) standards.

In an embodiment, an exemplary node is scanning as it listens for otherwireless nodes broadcasting on the short-range radio. An exemplaryscanning node may capture, for example, a MAC address of the advertisingnode, a signal strength of the RF output signal transmitted from theadvertising node, and any other metadata published by the advertisingnode (e.g., other information in the advertising data packet). Thoseskilled in the art will appreciate that the scope of “listening” when anode is scanning may vary. For example, the query may be limited. Inother words, the scope of what a node is particularly interested in andfor which it is listening may be focused or otherwise limited. In such acase, for example, the information collected may be limited toparticular information from a targeted population of short-rangewireless nodes advertising; but the information collection may beconsidered “open” where information from any advertising device iscollected.

When nodes are advertising or scanning, an embodiment may make furtheruse of status flags and additional modes when advertising or scanning aspart of how nodes communicate and may be managed. In one example, when ascanning (listening) node receives an advertising data packet with thestatus flag indicating an Alert Level 1 or 2 status, and the scanningnode is in “Passive” scanning mode, the node will switch to “Active”scanning mode for some interval. However, when the scanning node in thissituation is already in an “Active” scanning mode, the node will sendthe SCAN_REQ message and receive a SCAN_RSP from the advertising node(e.g., a message providing the additional information requested from theadvertising node). The scanning node will then switch back to a“Passive” scanning mode.

In another example, when an advertising (broadcasting) node receives aSCAN_REQ from a scanning node, the advertising node will consider thatits advertising data packet has been acknowledged. Further, theadvertising node will reset its “Alert” status flag back to an AlertLevel 0 status. This allows the advertising node to effectively receivean acknowledgement to its advertisement without ever making a connectionto the scanning node, which advantageously and significantly saves onpower consumption.

In yet another example, when a scanning node receives an advertisingdata packet with an Alert Level 3 status flag set, the scanning nodewill attempt to make a connection with the advertising device. Once theconnection is made, the advertising device will attempt to upload itsdata to the connected device

Thus, an embodiment of the node advertise and query (scan) logic managerof code 325 may rely upon one or more status flags, advertising modes,scanning modes, as nodes communicate with each other in variousadvantageous manners.

Node Information Control & Exchange Manager

In an exemplary embodiment, the information control and exchange managerpart of node control and management code 325 determines whether and howinformation may be exchanged between nodes. In the exemplary embodiment,the information control and exchange manager establishes different nodeoperational states where information may be changed according to adesired paradigm for the state. In more detail, an embodiment ofinformation control and exchange manager may establish different levelsof information exchange between nodes with a “non-connectableadvertising” state or mode of operation, a “discoverable advertising”state or mode, and a “general advertising” state or mode operation. Whena node is in the “non-connectable advertising” mode, the nodeinformation exchange is limited. For example, the advertising node maybroadcast information that is captured by one or more querying(scanning) nodes, but no two-way exchange of information happens.

When a node is in the “discoverable advertising” mode and a scanningnode is in “Active” mode, the node information exchange in enabled bothways. For example, the advertising node sends the advertising packet,and in response the scanning node sends the SCAN_REQ packet. After theadvertising node receives the SCAN_REQ requesting additionalinformation, the advertising node sends the SCAN_RSP with the requestedinformation. Thus, in the “discoverable advertising” mode there is atwo-way exchange of information, but no active connection is madebetween the two nodes exchanging information.

Finally, for advanced two-way information exchange, an active connectionmay be used between nodes and information may be exchanged both ways toand from different nodes. In a more detailed embodiment, at this levelof two-way information exchange, nodes are first identified and thenauthenticated as part of establishing the active connection. Onceauthenticated and thereafter actively connected to each other, the nodesmay securely share information back and forth. In one example, a sensornode uploading previously captured environmental information to a masternode may be in this mode or state. In another example, an ID nodeuploading the stored results of a node scanning operation to a masternode may be in this mode or state. In yet another example, a master nodesharing a timer and/or location information with corresponding nodes maybe in this mode or state.

Node Power Manager

In an exemplary embodiment, the node power manager part of node controland management code 325 focuses on managing power consumption and theadvantageous use of power (e.g., an adjustable level of RF output signalpower) in a node. In general, nodes are either powered by a battery(such as battery 355 in an ID node), or by an interface (such asbattery/power interface 470 in a master node) to an external powersource. Examples of an external power source may include, in someembodiments, power supplied from an outlet or power connection within afacility, or power generated onboard a conveyance (e.g., automobile,truck, train, aircraft, ship, etc.). Those skilled in the art willappreciate that an interface to an external power source will begenerally referred to as a “wired” power connection, and that node powermanager may be informed whether a node is wired or powered off abattery, such as battery 355. Further embodiments may implement aninterface to an external power source with wireless power transmission,such as via inductive coils.

In one embodiment, a node may manage power used when performing tasks.For example, a node may manage power when determining which node shouldperform a particular task. In more detail, the collective powerconsumption of a group of devices may be managed by electing to employwired nodes, when feasible or desired, to accomplish a particular task,and saving the battery-powered nodes for other less energy burdensome ortaxing tasks. In another embodiment, historic data may inform the systemof the power needed to accomplish a particular task, and the system maymake a determination of which node should accomplish the particular taskbased upon such historic data. In other embodiments, profile data mayalso be used to inform the system of the power needed to accomplish aparticular task (e.g., a sensor profile that describes powerrequirements for operation of a sensor node that gathers sensor dataover a certain period of time and under certain conditions). The systemmay also make a determination of which node should accomplish theparticular task based upon such profile data.

In another example, the exemplary node power manager may manage powerwhen determining how to best to use and adjust power to more accuratelyaccomplish a particular task. In one embodiment, an RF signal outputfrom a node (such as a short-range RF output signal from an ID node) mayperiodically move through a range of output power or simply switchbetween two or more settings that differ in a detectable manner. Asdisclosed in more detail below, the variability and dynamic adjustmentof RF output signal power may allow other nodes (such as one or moremaster nodes) to see each node at the upper range of the RF outputsignal power, and only see nodes physically close to the advertisingnode at the lower range of signal power.

In another example, the exemplary node power manager may cause a changeto a characteristic of its RF output signal power when the node has beenassociated to a physical place or another node by virtue of context data(such as context data 560 and association logic that utilizes that typeof information). In one embodiment, the node may be instructed to changehow often the node communicates and/or a characteristic of its RF outputpower to preserve power.

In yet another example, all advertising nodes may have their respectivenode power managers periodically cause each respective node to broadcastat a maximum RF output signal power level to ensure they still arewithin range of a scanning ID Node or Master Node. Doing so may increasethe chance of being in communication range and allows the individualnodes to be properly located and managed within the network. Thebroadcast duration may be set or dynamically changed to allow pairing tooccur if needed.

Rather than adjust the RF output signal power level, the exemplary nodepower manager may, in some embodiments, adjust the RF receiversensitivity of a node. This allows for an adjustable range of reception(as opposed to merely an adjustable range of broadcast), which maysimilarly be used to manage power and enhance location determinations asdiscussed herein.

In yet another embodiment, a combination approach may be used in whichthe node power manager may concurrently and independently adjust morethan one RF characteristic of a node. For example, en exemplary nodepower manager may adjust an RF output signal power level and also adjustthe RF receiver sensitivity of a node as the node is located andassociated with other nodes. Those skilled in the art will realize thatthis may be especially useful in an area with an unusually denseconcentration of nodes, and a combination of changing RF output signalpower levels

An embodiment of the exemplary node manager may refer to a power profile(e.g., an exemplary type of profile data 330, 430) when adjusting anode's power characteristics (e.g., consumption of power, use of power,output signal frequency, duty cycle of the output put signal, timing,power levels, etc.).

Node Association Manager

In an exemplary embodiment, the node association manager part of nodecontrol and management code 325 focuses on how the nodes associate withother nodes in conjunction and consistent with the server-sideassociation manager in code 525, as discussed in more detail below.Thus, exemplary node association manager, when executing in a node,directs how the node associates (e.g., enters an active connection mode)with one or more other nodes with input from the server.

The exemplary node association manager for a node may indicate through aStatus Flag if the node requires an acknowledgement or connection, or ifit has information available for upload to the backend. Thus, while anode may not be associated or actively connected yet to another node, astatus of the node may be inferred from, for example, the statusinformation in the node's broadcast header.

Regarding connections between nodes, there are generally secureconnections and unsecure connections. While an embodiment may allowunsecure connections between one or more sets of nodes, otherembodiments rely upon secure connections or authenticate pairings ofnodes. In one embodiment, for a node to pair with another node, theexemplary node association manager first identifies the nodes to beassociated and transmits an association request to the server. Therequest may include a specific request to pair the nodes and ask for thecorresponding pairing credentials from the server, such as server 100.The server 100 may have staged pairing credentials on particular nodesbased on information indicating the nodes would be within wirelessproximity and future pairing may occur. Visibility to the noderelationship may have been determined through scan-advertising, or3^(rd) party data such as barcode scan information indicating the nodesto be within proximity currently or at a future state.

When connecting or not connecting to exchange information under theexemplary node information exchange modes described above, nodesgenerally operate in a number of states, which make up an exemplaryadvertise cycle for an exemplary ID node. Such an exemplary advertisecycle for a node is further explained below with reference to FIG. 8 andin conjunction and consistent with the server-side association managerin code 525, as discussed in more detail below.

Airborne Mode Program Module

In one embodiment, node control and management code 325 may also includean airborne mode program module (not shown). In another embodiment, theairborne mode program module may be implemented as a part of the nodepower manager program module of code 325. An exemplary airborne modeprogram module generally operates to manage the output power of the IDnode's variable power short-range communication interface 375 when theID node is operating in an aircraft. Operating a wireless device withinan aircraft may, in some circumstances, have an unintentional impact onother electronic systems on the aircraft. In more detail, an embodimentof the airborne mode program module may operate to transition the IDnode from different states or modes depending upon particular operationsand/or operational conditions of the aircraft. For example, an exemplaryairborne mode program module may operate to transition the ID node fromone state or mode (e.g., a normal mode prior to takeoff, a disabled modeduring takeoff, an airborne mode while aloft, a disabled mode duringdescent, and a normal mode after landing) based upon detectedenvironmental conditions (e.g., pressure, altitude) and/or flight detailinformation associated with the aircraft. In this way, an ID node may beallowed to normally operate when onboard an aircraft, be disabled fromoperating at all in some circumstances, and be able to operate in anairplane mode that allows sensing and sensor data capture, but that maylimit transmission of an RF output signal to avoid interference with theaircraft's onboard electronics. Further information related to a methodof managing a wireless device (such as an ID node) in an aircraft isdisclosed in greater detail in U.S. patent application Ser. No.12/761,963 entitled “System and Method for Management of WirelessDevices Aboard an Aircraft,” which is hereby incorporated by reference.

Node Data

As previously noted, volatile memory 320 may also include certain data(e.g., profile data 330, security data 335, association data 340, shareddata 345, sensor data, and the like) generated as the ID node 120 aexecutes instructions as programmed or loaded from memory storage 315.In general, data used on a node, such as an ID node, may be receivedfrom other nodes or generated by the node during operations.

In one embodiment, profile data 330 is a type of data that defines ageneral type of behavior for an ID node, such as a Broadcast Profile(discussed in more detail below). In another embodiment where ID node120 a is a BLE device, profile data 330 may include a Bluetooth®compatible profile related to battery service (exposing the state of abattery within a device), proximity between BLE devices, or messagingbetween BLE devices. Thus, exemplary profile data 330 may exist involatile memory 320 and/or memory storage 315 as a type of data thatdefines parameters of node behavior.

In one embodiment, it may be desired to allow secured pairings of nodes.As will be explained in more detail below, as part of secure pairing ofnodes, a request for pairing credentials is generated and sent to server100. Thus, exemplary security data 335 (e.g., PIN data, securitycertificates, keys, etc.) may exist in volatile memory 320 and/or memorystorage 315 as a type of data associated with providing securedrelationships between nodes, such as the requested security credentials.

Association data, such as association data 340, generally identifies aconnected relationship between nodes. For example, ID node 120 a maybecome associated with the master node 110 a as the ID node 120 a moveswithin range of the master node 110 a and after the server directs thetwo nodes to associate (with authorization). As a result, informationidentifying the relationship between ID node 120 a and master node 110 amay be provided to server 100 and may be provided, as some point, toeach of ID node 120 a and master node 110 a. Thus, exemplary associationdata 340 may exist in volatile memory 320 and/or memory storage 315 as atype of data identifying associations between nodes.

Shared data 345 may exist in volatile memory 320 and/or memory storage315 as a type of data exchanged between nodes. For example, context data(such as environmental data) may be a type of shared data 345.

Sensor data 350 may also exist in volatile memory 320 and/or memorystorage 315 as a type of data recorded and collected from an onboardsensor or from another node. For example, sensor data 350 may includetemperature readings from a temperature sensor onboard an ID node and/orhumidity readings from a humidity sensor in another ID node (e.g., fromanother of the ID nodes within container 210 as shown in FIG. 2).

Thus, an ID node (such as node 120 a shown in FIG. 3) is a lower costwireless node that communicates with other ID nodes and master nodes viaa short-range radio with variable RF characteristics, can be associatedwith other nodes, can broadcast to and scan for other nodes, associatedwith other nodes, and store/exchange information with other nodes.

Master Node

A master node, such as master node 110 a shown in more detail in FIG. 4,shares many ID node features but generally expands upon them in order tofunction as a bridge to the server 100. In general, while an ID node isa type of lower level node in an exemplary wireless node network, amaster node is a type of higher level node. An exemplary master node maybe in a fixed location or otherwise stationary, while other examplemaster nodes may be implemented as movable and mobile devices.

Referring now to FIG. 4, exemplary master node 110 a comprises aprocessing or logic unit 400 coupled to a short-range communicationinterface 485, memory storage 415, volatile memory 420, clock/timer 460,and battery/power interface 470. In some embodiments, the short-rangecommunication interface 485 may have variable power characteristics,such as receiver sensitivity and RF output power level. Those skilled inthe art will appreciate that processing unit 400 is logic, such as amicroprocessor or microcontroller, which generally performs computationson data and executes operational and application program code and otherprogram modules within the master node 110 a.

In general, those skilled in the art will appreciate that thedescription of hardware with respect to ID node 110 a in FIG. 4 appliesto the similar hardware and software features appearing in each type ofnode, including a master node. Those skilled in the art will appreciatethat exemplary master node 110 a is a hardware-based component that mayimplement processor 400 with a single processor or logic unit, a morepowerful multi-core processor, or multiple processors depending upon thedesired implementation. In one embodiment, processing unit 400 may beimplemented with a low power microprocessor and associated peripheralcircuitry. Less complex microcontrollers or discrete circuitry may beused to implement processing unit 400 as well as more complex andsophisticated general purpose or dedicated purpose processors.

In yet another embodiment, exemplary processing unit 400 may beimplemented by a low power ARM1176JZ-F application processor used aspart of a single-board computer, such as the Raspberry Pi Computer ModelB-Rev-2. The ARM application processor is embedded within a Broadcom®BCM2835 system-on-chip (SoC) deployed in the Raspberry Pi Computer. Inthis embodiment, the Raspberry Pi Computer device operates as a core ofexemplary master node 110 a and includes a Secure Digital memory cardslot and flash memory card operating as memory storage 415, a 512 MbyteRAM memory storage operating as volatile memory 420, an operating system(such as Linux) stored on memory storage 415 and running in volatilememory 420, and peripherals that implement clock/timer 460, and a powersupply operating as a power interface 470.

Like short-range interface 375 in ID node 120 a, exemplary master node110 a includes a short-range communication interface 480 as aprogrammable radio and an omni-directional antenna coupled to theprocessing unit 400. In some embodiments, the short-range communicationinterface 480 may have variable RF power characteristics, such asreceiver sensitivity and/or RF output signal power level. In someembodiments, interface 480 may use an antenna with a different antennaprofile when directionality may be desired. Examples of short-rangecommunication interface 480 may include other hardware (not shown) foroperatively coupling the device to a specific short-range communicationpath (e.g., a Bluetooth® Low Energy (BLE) connection path communicatingat 2.4 GHz). While BLE is used in one embodiment to enable a short-rangecommunication protocol, variable power short-range interface 480 may beimplemented with other low power, short-range communication protocols,such as ultra-low power communication protocols used with ultra-widebandimpulse radio communications, ZigBee protocols, IEEE 802.15.4 standardcommunication protocols, and the like.

In one embodiment, various RF characteristics of the radio'stransceiver, such as the RF output power and the RF receiver sensitivitymay be dynamically and programmatically varied under control ofprocessing unit 400. In other embodiments, further RF characteristics ofthe radio's transceiver may be programmatically varied, such asfrequency, duty cycle, timing, modulation schemes, spread spectrumfrequency hopping aspects, etc., as needed to flexibly adjust the RFoutput signal as needed depending upon a desired implementation andanticipated use of exemplary master node 110 a. In other words,embodiments of master node 110 a (or any other master node) may haveprogrammatically adjustable RF characteristics (such as an adjustable RFoutput signal power, an adjustable RF receiver sensitivity, the abilityto switch to a different frequency or frequency band, etc.).

In addition to the short-range communication interface 480, exemplarymaster node 110 a includes a medium and/or long-range communicationinterface 485 to provide a communication path to server 100 via network105. In one embodiment, communication interface 485 may be implementedwith a medium range radio in the form of an IEEE 802.11g compliant WiFitransceiver. In another embodiment, communication interface 485 may beimplemented with a longer range radio in the form of a cellular radio.In yet another embodiment, both a WiFi transceiver and a cellular radiomay be used when best available or according to a priority (e.g., firstattempt to use the WiFi transceiver if available due to possible lowercosts; and if not, then rely on the cellular radio). In other words, anembodiment may rely upon the longer range cellular radio part ofinterface 485 as an alternative to the medium range WiFi transceiverradio, or when the medium range radio is out of reach from a connectinginfrastructure radio within network 105. Thus, in these embodiments,medium and/or long-range communication interface 485 may be used tocommunicate captured node information (e.g., profile data 430,association data 440, shared data 445, sensor data 450, and locationdata 455) to server 100.

The battery/power interface 470 for master node 110 a generally powersthe circuitry implementing master node 110 a. In one embodiment,battery/power interface 470 may be a rechargeable power source. Forexample, a master node may have a rechargeable power source along with asolar panel that charges the power source in order to help facilitatedeployment of the master in a remote location. In another embodiment,battery/power interface 470 may be a non-rechargeable power sourceintended to be disposed of after use. In yet another embodiment,battery/power interface 470 may be a power interface connector (such asa power cord and internal power supply on master node 110 a). Thus, whenan exemplary master node is in a fixed or stationary configuration, itmay be powered by a power cord connected to an electrical outlet, whichis coupled to an external power source. However, other mobile masternodes may use an internal power source, such as a battery.

The clock/timer 460 for master node 110 a generally provides one or moretiming circuits used in, for example, time delay, pulse generation, andoscillator applications. In an embodiment where master node 110 aconserves power by entering a sleep or dormant state for a predeterminedtime period as part of overall power conservation techniques,clock/timer 460 assists processing unit 400 in managing timingoperations.

Optionally, an embodiment may also implement master node 110 a asincluding one or more sensors 465 (similar to sensors deployed on IDnode based Sensor nodes and described above with respect to FIG. 3).Additionally, an embodiment of master node 110 a may also provide a userinterface 405 to indicate status and allow basic interaction for reviewof captured node data and interaction with nodes and server 100. In oneembodiment, user interface 405 may provide a display, interactivebuttons or soft keys, and a pointing device to facilitate interactionwith the display. In a further embodiment, a data entry device may alsobe used as part of the user interface 405. In other embodiments, userinterface 405 may take the form of one or more lights (e.g., statuslights), audible input and output devices (e.g., a microphone andspeaker), or touchscreen.

As previously noted, an exemplary master node, such as master node 110a, may be positioned in a known fixed location or, alternatively,includes dedicated location positioning circuitry 475 (e.g., GPScircuitry) to allow the master node self-determine its location or todetermine its location by itself. In other embodiments, alternativecircuitry and techniques may be relied upon for location circuitry 475(rather than GPS), such as location circuitry compatible with othersatellite-based systems (e.g., the European Galileo system, the RussianGLONASS system, the Chinese Compass system), terrestrial radio-basedpositioning systems (e.g., cell phone tower-based or WiFi-basedsystems), infrared positioning systems, visible light based positioningsystems, and ultrasound-based positioning systems).

Regarding memory storage 415 and volatile memory 420, both areoperatively coupled to processing unit 400 in exemplary master node 110a. Both memory components provide program elements used by processingunit 400 and maintain and store data elements accessible to processingunit 400 (similar to the possible data elements stored in memory storage315 and volatile memory 320 for exemplary ID node 120 a).

In the embodiment shown in FIG. 4, memory storage 415 maintains avariety of executable program code (e.g., master control and managementcode 425), data similar to that kept in an ID node's memory storage 315(e.g., profile data 430, security data 435, association data 440, shareddata 445, sensor data 450, and the like) as well as other data morespecific to the operation of master node 110 a (e.g., location data 455that is related to the location of a particular node). Like memorystorage 315, memory storage 415 is a tangible, non-transient computerreadable medium on which information (e.g., executable code/modules,node data, sensor measurements, etc.) may be kept in a non-volatile andnon-transitory manner.

Like volatile memory 320 in ID node 120 a, volatile memory 420 istypically a random access memory (RAM) structure used by processing unit400 during operation of the master node 110 a. Upon power up of masternode 110 a, volatile memory 120 may be populated with an operationalprogram (such as master control and management code 425) or specificprogram modules that help facilitate particular operations of masternode 110 a. And during operation of master 110 a, volatile memory 420may also include certain data (e.g., profile data 430, security data435, association data 440, shared data 445, sensor data 450, and thelike) generated as the master node 110 a executes instructions asprogrammed or loaded from memory storage 415.

Master Control & Management Code

Generally, an embodiment of master control and management code 425 is acollection of software features implemented as programmatic functions orprogram modules that generally control the behavior of a master node,such as master node 110 a. In one embodiment, master control andmanagement code 425 generally comprises several programmatic functionsor program modules including (1) a node advertise and query (scan) logicmanager, which manages how and when a node communicates; (2) aninformation control and exchange manager, which manages whether and howinformation may be exchanged between nodes; (3) a node power manager,which manages power consumption and aspects of RF output signal powerand/or receiver sensitivity for variable short-range communications; (4)an association manager focusing on how the node associates with othernodes; and (5) a location aware/capture module to determine nodelocation.

Master Node Program Modules and ID Node Modules

In an exemplary embodiment, program modules (1)-(4) of master nodecontrol and management code 425 generally align with the functionalityof similarly named program modules (1)-(4) of node control andmanagement code 325 as described above with respect to FIG. 3.Additionally, as node control and management code 325 may also comprisean airborne mode program module, those skilled in the art willappreciate and understand that master node control and management code425 may also comprise a similar functionality airborne mode programmodule in order to allow advantageous operations of a master node whileairborne. However, and consistent with examples set forth below, suchmodules may have some differences when in a master node compared withthose controlling an ID node.

Location Aware/Capture Module

In addition to exemplary program modules (1)-(4) of code 425, anexemplary embodiment of master node control and management code 425 willfurther comprise an exemplary location aware/capture module related tonode location (more generally referred to as a location manager modulefor a master node). In general, the exemplary location aware/capturemodule deployed in an exemplary master node may determine its ownlocation and, in some embodiments, the location of a connected node.Embodiments of the exemplary location aware/capture module may work inconjunction with location manager program code residing and operating ina server (e.g., as part of server control and management code 525) whendetermining node locations of other nodes, as discussed in more detailherein.

In one embodiment, a master node may be positioned in a known, fixedlocation. In such an embodiment, the exemplary location aware/capturemodule may be aware that the master node location is a known, fixedlocation, which may be defined in a fixed, preset, or preprogrammed partof memory storage 415 (e.g., information in the location data 455maintained in memory storage 415). Examples of such location informationmay include conventional location coordinates or other descriptivespecifics that identify the location of the master node. In anotherembodiment where the master node may not be inherently known or a fixedlocation at all times (e.g., for a mobile master node), the exemplarylocation aware/capture module may communicate with location circuitry,such as GPS circuitry 475 on a master node, to determine the currentlocation of the master node.

In an embodiment, the location of the master node may be communicated tothe server, which may use this location information as part of managingand tracking nodes in the wireless node network. For example, if anexemplary master node is mobile and has determined a new currentlocation using location circuitry 475, the master node may provide thatnew current location for the master node to the server. Additionally,when the master node's exemplary location aware/capture moduledetermines the location of a node associated with the master node, themaster node may also provide the location of that node associated withthe master node to the server.

Server

While FIGS. 3 and 4 illustrate details of hardware and software aspectsof an exemplary ID node and exemplary master node, respectively, FIG. 5provides a more detailed diagram of an exemplary server that may operateas part of an exemplary wireless node network in accordance with anembodiment of the invention. In an exemplary embodiment, server 100 maybe referred to as an Association and Data Management Server (ADMS) thatmanages the nodes, collects information from the nodes, stores thecollected information from the nodes, maintains or has access to contextdata related to the environment in which the nodes are operating, andmay provide information about the nodes (e.g., status, sensorinformation, etc.) to requesting entities. Further details on variousembodiments that take advantage of this functionality are explainedbelow. Those skilled in the art will appreciate that node density,geographic installation characterization, and network connectively areall types of examples of factors that may impact a final architecturedesired for an embodiment of a wireless node network.

Referring now to FIG. 5, exemplary server 100 is shown as a networkedcomputing platform capable of connecting to and interacting with atleast the wireless master nodes. In other embodiments, exemplary server100 is also capable of connecting to and interacting with one or moreuser access devices. Those skilled in the art will appreciate thatexemplary server 100 is a hardware-based component that may beimplemented in a wide variety of ways. For example, server 100 may use asingle processor or may be implemented as one or more part of amulti-processor component that communicates with devices (such as useraccess devices 200, 205) and wireless nodes (such as master node 110 a).

In general, those skilled in the art will further appreciate that server100 may be implemented as a single computing system, a distributedserver (e.g., separate servers for separate server related tasks), ahierarchical server (e.g., a server implemented with multiple levelswhere information may be maintained at different levels and tasksperformed at different levels depending on implementation), or a serverfarm that logically allows multiple distinct components to function asone server computing platform device from the perspective of a clientdevice (e.g., devices 200, 205 or master node 110 a). In some regionaldeployments, an exemplary server may include servers dedicated forspecific geographic regions as information collected within differentregions may include and be subject to different regulatory controls andrequirements implemented on respective regional servers.

Likewise, while the embodiment shown in FIG. 5 illustrates a singlememory storage 515, exemplary server 100 may deploy more than one memorystorage media. And memory storage media may be in differingnon-transitory forms (e.g., conventional hard disk drives, solid statememory such as flash memory, optical drives, RAID systems, cloud storageconfigured memory, network storage appliances, etc.).

At its core, exemplary server 100 shown in FIG. 5 comprises a processingor logic unit 500 coupled to a network interface 590, which facilitatesand enables operative connections and communications through network 105with one or more master nodes as well as, in some embodiments, useraccess devices, such as devices 200, 205. In one embodiment, server 100may include a medium and/or long-range communication interface 595 withwhich to more directly communicate with one or more master nodes. Usingthese communication paths as well as program code or program modules(such as server control and management code 525), the server 100generally operates to coordinate and manage information related to an IDnode as an item associated with the ID node physically moves from onelocation to another.

As a computing platform, the processing unit 500 of exemplary server 100is operatively coupled to memory storage 515 and volatile memory 520,which collectively store and provide a variety of executable programcode (e.g., server control and management code 525), data similar tothat kept in a master or ID node's respective memory storage (e.g.,profile data 530, security data 535, association data 540, shared data545, sensor data 550, location data 555) and context data 560 related tothe environment in which the nodes are operating (e.g., informationgenerated from within the wireless node network and information createdexternal to the wireless node network).

Like memory storage 315 and storage 415, memory storage 515 is atangible, non-transient computer readable medium on which information(e.g., executable code/modules (e.g., server control and management code525), node-related data (e.g., profile data 530, security data 535,association data 540, location data 555, etc.), measurement information(e.g., a type of shared data 545, sensor data 550, etc.), andinformation on the contextual environment for the nodes (e.g., contextdata 560) may be kept in a non-volatile and non-transitory manner.

Those skilled in the art will appreciate that the above identificationof particular program code and data are not exhaustive and thatembodiments may include further executable program code or modules aswell as other data relevant to operations of a processing-based device,such as an ID node, a master node, and a server.

Context Data

As noted above, server 100 may access context data 560 as part ofmanaging nodes in the wireless node network. The exemplary server 100may contain a collection of such context data 560 in a context database565 according to an embodiment. As illustrated in FIG. 5, exemplarycontext database 565 is a single database accessible by processing unit500 internal to server 100. Those skilled in the art will readilyunderstand that other configurations that provide an accessiblecollection of context data 560 are possible and contemplated within thescope and principles of embodiments of the invention. For example,context database 565 may be an externally accessible database (ormultiple databases), such as an accessible storage maintained outsidethe server 100 via a dedicated interface or a network storage device (ornetwork attached storage (NAS) unit). In yet another embodiment, thecontext database may be separately maintained by an external databaseserver (not shown) that is distinct from server 100, but accessiblethrough a communication path from server 100 to a separate databaseserver (e.g., via network 105). Furthermore, those skilled in the artwill appreciate that context database 565 may be implemented with cloudtechnology that essentially provides a distributed networked storage ofcollections of information (such as context data 560, sensor data 550,shared data 545, etc.) accessible to server 100.

Within context database 565, an exemplary embodiment of the collectionof context data 560 may be maintained that generally relates to anenvironment in which the nodes are operating or anticipated to beoperating. In more detail, the context data 560 may generally relate towhat a similar node has experienced in a similar environment to what agiven node is presently experiencing or is anticipated to experience asthe given node moves.

In a general example, an environment in which a node may be actually oranticipated to be operating may include different types ofenvironments—for example, an electronic communication environment (e.g.,an RF environment that may be cluttered with signals or includematerials or structure that may impede or otherwise shield RFcommunications), a physical environment of an anticipated path alongwith the identified node moves (e.g., temperature, humidity, security,and other physical characteristics), a conveyance environment related tohow a node may move or be anticipated to be moving (e.g., speed andother parameters of a truck, airplane, conveyor system), and a densityenvironment related to the density of nodes within an area near aparticular node (e.g., how many nodes are anticipated to occupy acorridor, such as structure 2200 shown in FIG. 22A, or a storagefacility through which a particular ID node is anticipated to transit onits shipping path).

In light of these different aspects of a node's operating environment,exemplary context data 560 may provide information related to differentstructures and conditions related to movement of an item (e.g., aparticular type of courier device, vehicle, facility, transportationcontainer, etc.). Such information may be generated by an entityoperating the wireless node network, such as a shipping company.Additionally, exemplary context data 560 may include third party datagenerated external to the wireless node network. Thus, context data,such as data 560, may include a wide variety of data that generallyrelates to the environment in which the nodes are operating and may beused to advantageously provide enhanced node management capabilities inaccordance with embodiments of the present invention.

In general, FIG. 5 illustrates exemplary types of context data 560 beingmaintained in database 565 and in volatile memory 520. Those skilled inthe art will appreciate that context data 560 may also be maintained inother data structures, in addition to or instead of maintaining suchinformation in a database. As illustrated in FIG. 5, exemplary types ofcontext data 560 may include but are not limited to scan data 570,historic data 575, shipment data 580, layout data 585, RF data 587, and3^(rd) party data.

Scan data 570 is generally data collected for a particular item relatedto an event. For example, when an item is placed in a package (such aspackage 130), a label may be generated and placed on the exterior of thepackage. The label may include a visual identifier that, when scanned byan appropriate scanning device capable of capturing, identifies thepackage. The information generated in response to scanning theidentifier (a type of event), may be considered a type of scan data.Other scan data 570 may include, for example, general inventory datagenerated upon manual entry of information related to the package;captured package custodial control data; and bar code scan data.

Historic data 575 is generally data previously collected and/or analyzedrelated to a common characteristic. Historic data 575 embodiesoperational knowledge and know-how for a particular characteristicrelevant to operations of the wireless node network. For example, thecommon characteristic may be a particular event (e.g., movement of anitem from an open air environment to within a particular closedenvironment, such as a building), a type of item (e.g., a type ofpackage, a type of content being shipped, a location, a shipment path,etc.), a success rate with a particular item (e.g., successfulshipment), and the like. Another example of historic data 575 mayinclude processing information associated with how an item has beenhistorically processed as it is moved from one location to another(e.g., when moving within a particular facility, processing informationmay indicate the item is on a particular conveyor and may includeinformation about the conveyor (such as speed and how long it isanticipated the item will be on the conveyor)).

Shipment data 580 is generally data related to an item being moved fromone location to another location. In one embodiment, shipment data 580may comprise a tracking number, content information for an item beingshipped, address information related to an origin and destinationlocations, and other characteristics of the item being moved.

Layout data 585 is generally data related to the physical area of one ormore parts of an anticipated path. For example, an embodiment of layoutdata 585 may include building schematics and physical dimensions ofportions of a building in which a node may be transiting. An embodimentmay further include density information associated with physical areasto be transited and anticipated numbers of potential nodes in thoseareas as types of layout data. In another example, an embodiment oflayout data may include a configuration of how a group of packages maybe assembled on a pallet, placed into a shipping container (e.g., a unitload device (ULD)) that helps move a collection of items on variousforms with single mode or intermodal transport.

RF data 587 is generally signal degradation information about a signalpath environment for a particular type of node and may relate toparticular adverse RF conditions that may cause signal fluctuations,interference, or other degradation from the otherwise optimal signalpath environment for that type of node. For example, RF data may includeshielding effects when using a particular packaging or location,shielding effects when the package is within a particular type ofcontainer or assembled as part of a palletized shipment, shieldingeffects when particular content is shipped, and other physical andelectronic interference factors.

Third party data 589 is an additional type of context data 560 thatgenerally includes data generated outside the network. For example,third party data may include weather information associated withparticular areas to be transited as the item is moved along ananticipated path from one location to another. Those skilled in the artwill appreciate other types of third party data that relate to physicaland environmental conditions to be faced by an item being moved from onelocation to another may also be considered context data 560.

The use of context data, such as context data 560 described above,advantageously helps server 100 better manage movement of items, providebetter location determination, enhance intelligent operation andmanagement of different levels of the wireless node network, and provideenhanced visibility to the current location and status of the itemduring operation of the wireless node network. In one embodiment, servercontrol and management code 525 may provide such functionality thatenables the wireless node network to be contextually aware andresponsive.

Server Control & Management Code

Generally, server control and management code 525 controls operations ofexemplary server 100. In an embodiment, server control and managementcode 525 is a collection of software features implemented asprogrammatic functions in code or separate program modules thatgenerally control the behavior of server 100. Thus, exemplary servercontrol and management code 525 may be implemented with severalprogrammatic functions or program modules including, but not limited to,(1) a server-side association manager, which provides a framework formore robust and intelligent management of nodes in the wireless nodenetwork; (2) a context-based node manager, which enhances management ofnodes in the wireless node network based upon context data; (3) asecurity manager, which manages secure pairing aspects of nodemanagement; (4) a node update manager, which provides updated ordifferent programming for a particular node and shares information withnodes; (5) a location manager for determining and tracking the locationof nodes in the network; and (6) an information update manager, whichservices requests for information related to the current status of anode or generally providing information about a node or collected from anode.

Server-Side Association Manager

The server-side association manager (also referred to as a server-sideassociation management function) is generally a program module inexemplary code 525 that is responsible for intelligently managing thenodes in the wireless node network using a secure information framework.In an embodiment, this framework may be implemented to be acontext-driven, learning sensor platform. The framework may also enablea way for information (such as RF scan, location, date/time, and sensordata) to be securely shared across nodes, a way to change the behaviorof a node, and for a node to know it is considered “missing.” Theframework established during operation of the server-side associationmanager allows the network of nodes to be managed as a system withenhanced and optimized accuracy of determining the physical location ofeach ID Node. Further information regarding particular embodiments ofsuch an association management framework and methods are explained belowin more detail.

Context-Based Association Manager

The context-based node manager is generally a program module inexemplary code 525 that is responsible for incorporating context data aspart of management operations to provide an enhanced data foundationupon which visibility of the nodes may be provided. In some embodiments,the context-based node manager may be implemented as part of theserver-side association manager while other embodiments may implementthe context-based node manager as a separate program module.

In one embodiment, the enhanced data foundation relies upon contextdata, such as context data 560 (e.g., scan data 570, historic data 575,shipment data 580, layout data 585, and other third party contextualdata providing information regarding the conditions and environmentsurrounding an item and ID node moving from one location to another.Such context data (e.g., the network know-how, building layouts, andoperational knowledge of nodes and shipping paths used with the wirelessnode network) may provide the enhanced building blocks that allow theserver 100 to manage tracking and locating of nodes in a robustlyenriched contextual environment. In an embodiment, context-basedmanagement provides visibility to the system through data analysis forwhen and how associations should be expected as the nodes travel throughthe wireless node network. In other embodiments, it may provide thefoundation for better understanding RF signal degradation, which can becaused by the operating environment, packaging, package content, and/orother packages related to an item and its ID node.

Security Manager

The security manager module, which may be implemented separately or aspart of the association manager module in exemplary server control andmanagement code 525, helps with associating two nodes in the wirelessnode network by managing aspects of secure pairing of the nodes. In oneembodiment, security manager module provides the appropriate pairingcredentials to allow a node to securely connect to another node. Thus,when a node desires to connect to another node, an embodiment requiresappropriate pairing credentials be generated by the server, provided tothe nodes, and observed within the nodes to allow for a successfulconnection or association of nodes.

In operation, a node (such as master node 110 a) identifies the addressof the node (such as ID node 120 a) to whom it desires to connect. Withthis address, the node prepares a pairing request and sends the requestto the server 110. The server 100 operates under the control of thesecurity manager module of the association manager, and determineswhether the requesting node should be connected or otherwise associatedwith the other node. If not, the server does not issue the requestedsecurity credentials. If so and in accordance with the desiredassociation management paradigm set by the association manager of code525, server provides the requested credentials necessary for asuccessful wireless pairing and the establishment of securecommunications between the associated nodes.

Node Update manager

The exemplary server control and management code 525 may include a nodeupdate manager module that provides updated programming information tonodes within the wireless node network and collects information fromsuch nodes (e.g., shared data 545, sensor data 550). The node updatemodule may be implemented separately or as part of the associationmanager module in exemplary server control and management code 525.

Providing an update to a node's programming may facilitate and enabledistribution of node functions to save power and better manage the nodesas a system. For example, one embodiment may alter the functionalresponsibility of different nodes depending on the context orassociation situation by temporarily offloading responsibility for aparticular function from one node to another node. Typically, the serverdirects other nodes to change functional responsibility. However, insome embodiments, a master node may direct other nodes to alterfunctional responsibility.

Sharing information between nodes and with server (e.g., via anexemplary node update manager) facilitates collecting information from anode and sharing information with other nodes as part of an associationmanagement function of server 100. For example, one embodiment maycollect and share RF scan data (a type of shared data 545), informationabout a node's location (a type of location data 555), systeminformation about date/time (another type of shared data 545), andsensor measurements collected from sensor nodes (a type of sensor data550).

Location Manager

The exemplary server control and management code 525 may include alocation manager module that helps determine and track node locations.In a general embodiment, the location of a node may be determined by thenode itself (e.g., a master node's ability to determine its own locationvia location circuitry 475), by a node associated with that node (e.g.,where a master node may determine the location of an ID node), by theserver itself (e.g., using location information determined by one ormore techniques implemented as part of code 525), and by a combinedeffort of a master node and the server.

In general, an exemplary ID node may be directly or indirectly dependenton a master node to determine its actual physical location. Embodimentsmay use one or more methodologies to determine node location. Forexample and as more specifically described below, possible methods fordetermining node location may relate to controlling an RF characteristicof a node (e.g., an RF output signal level and/or RF receiversensitivity level), determining relative proximity, consideringassociation information, considering location adjustments for contextinformation and an RF environment, chaining triangulation, as well ashierarchical and adaptive methods that combine various locationmethodologies. Further information and examples of how an exemplarylocation manager module may determine a node's location in accordancewith such exemplary techniques are provided in more detail below.

Additionally, those skilled in the art will appreciate that it may alsobe possible to determine what constitutes an actionable location versusactual location based upon contextual information about the item beingtracked. For example, a larger item may require relatively less locationaccuracy than a small item such that operational decisions and statusupdates may be easier implemented with knowledge of context. If the sizeof the item is known, the location accuracy can be tuned accordingly.Thus, if a larger item is to be tracked, or if the system's contextualawareness of it is such that lower location accuracy can be used, astronger signal and thus wider area of scanning may be employed, whichmay help in situations where RF interference or shielding is an issue.

Information Update Manager

The exemplary server control and management code 525 may include aninformation update manager module that provides information related tooperations of the wireless node network and status of nodes. Suchinformation may be provided in response to a request from a deviceoutside the wireless node network (such as user access device 200). Forexample, someone shipping an item may inquire about the current statusof the item via their laptop or smartphone (types of user accessdevices), which would connect to server 100 and request suchinformation. In response, the information update manager module mayservice such a request by determining which node is associated with theitem, gathering status information related to the item (e.g., locationdata, etc.), and provide the requested information in a form that istargeted, timely, and useful to the inquiring entity.

In another example, a user access device may connect to server 100 andrequest particular sensor data from a particular node. In response,information update manager may coordinate with node update manager, andprovide the gathered sensor data 545 as requested to the user accessdevice.

Node Filtering Manager

An embodiment of exemplary server control and management code 525 mayoptionally comprise a node filtering manager, which helps manage thetraffic of nodes with a multi-level filtering mechanism. The filteringessentially sets up rules that limit potential associations andcommunications. An example of such a node filtering management maydefine different levels or modes of filtering for a master node (e.g.,which ID nodes can be managed by a master node as a way of limiting thecommunication and management burdens on a master node).

In one example, a “local” mode may be defined where the ID node onlycommunicates and is managed by the assigned master node at the locationwhere the last wireless node contact back to server 100 and/or wherethird party data indicates the assigned master node and ID node are inphysical and wireless proximity. Thus, for the “local” mode of trafficfiltering, only the assigned master node communicates and processesinformation from a proximately close and assigned ID node.

Moving up to a less restrictive filtering mode, a “regional” mode offiltering may be defined where the ID node may communicate and bemanaged by any master node at the location last reported back to server100 and/or where third party data indicates the ID node is located.Thus, for the “regional” mode of traffic filtering, any master node nearthe ID node may communicate and process information from that ID node.This may be useful, for example, when desiring to implement a limit onassociations and pairings to within a particular facility.

At the least restrictive filtering mode, a “global” mode of filteringmay be defined as essentially system-wide communication where the IDnode may be allowed to communicate and be managed by any master node. Inother words, the “global” mode of traffic filtering allows any ID nodewithin the wireless node network to communicate information through aparticular master node near the ID node may communicate and processinformation from that ID node.

Thus, with such exemplary filtering modes, an ID node in a certaincondition (e.g., distress, adverse environmental conditions, adverseconditions of the node, etc.) may signal the need to bypass anyfiltering mechanism in place that helps manage communications andassociation by using the “Alert” Status Flag. In such an example, thiswould operate to override any filtering rules set at the Master Nodelevel in order to allow an ID node to be “found” and connect to anothernode.

Thus, exemplary server 100 is operative, when executing code 525 andhaving access to the types of data described above, to manage the nodes,collect information from the nodes, store the collected information fromthe nodes, maintain or have access to context data related to theenvironment in which the nodes are operating, and provide informationabout the nodes (e.g., status, sensor information, etc.) to a requestingentity.

Node Communication & Association Examples

To better illustrate how exemplary management and communicationprinciples may be implemented within an exemplary wireless node network,FIGS. 8-12 provide several examples of how exemplary components of thewireless node network may generally communicate (advertising &scanning), associate, and exchange information during different types ofoperations in various embodiments. FIGS. 22A-C also provide a moredetailed application of such exemplary association and communicationactivities when an exemplary ID node moves along a transit path (e.g.,through a corridor) and is tracked and managed by different master nodesand a server in an embodiment.

Node Advertising Cycle Example

As generally explained above, a node may have several different types ofadvertising states in which the node may be connectable with other nodesand may communicate with other nodes. And as a node moves within awireless node network, the node's state of advertising and connectionmay change as the node disassociates with a previously connected node,associates with a new node, or finds itself not associated with othernodes. In some situations, a node may be fine and in normal operationnot be connected or associated with another node. However, in othersituations, a node may raise an issue with potentially being lost if ithas not connected with any other node in a very long period of time. Assuch, a node may go through different types of advertising states inthese different operational situations.

Generally, a node may be in a state where it is not connectable withother nodes for a certain period of time (also referred to as anon-connectable interval). But later, in another state, the node maywant to be connected and advertises as such for a defined connectableperiod (also referred to as a connectable interval). As the nodeadvertises to be connected, the node may expect to be connected at somepoint. In other words, there may be a selectable time period withinwhich a node expects to be connected to another node. However, if thenode is not connected to another node within that period of time(referred to as an Alert Interval), the node may need to take specificor urgent action depending upon the circumstances. For example, if anode has not been connected to another node for 30 minutes (e.g., anexample alert interval), the node may change operation internally tolook “harder” for other nodes with which to connect. More specifically,the node may change its status flag from an Alert Level 0 (no issue,operating normal) to Alert Level 2 in order to request that anyavailable master node acknowledge receipt of the advertisement packetbroadcasted by the node seeking a connection.

FIG. 8 is a diagram illustrating exemplary advertising states (orinformation exchange and node connectability states) and factorsinvolved in transitions between the states by an exemplary ID node in awireless node network in accordance with an embodiment of the invention.Referring now to FIG. 8, three exemplary states for a node areillustrated as part of an exemplary advertising cycle for thenode—namely, an ID Node Non-Connectable Advertising state 805, an IDNode Discoverable Advertising state 815, and an ID Node GeneralAdvertising state 830. Transitions between these states will depend onfactors related to expirations of the types of intervals describedabove. In an embodiment, the duration of each of these intervals willdepend upon the system implementation and the contextual environmentwithin which the ID node is operating. Such time intervals may, forexample, be set by server 100 as part of data (e.g., profile data,association data, context data) provided to the node when updating thenode and managing operations of the node.

Referring to the example illustrated in FIG. 8, an exemplary ID node mayhave an alert interval set at, for example, 30 minutes, and be in IDNode Non-Connectable Advertising state 805 with a non-connectableinterval set at 5 minutes. In state 805, the ID node may broadcast oradvertise, but is not connectable and will not receive a SCAN_REQmessage (a type of request for more information sent to the advertisingnode from another node). Thus, the ID node in state 805 in this examplemay advertise in a non-connectable manner for at least 5 minutes butexpects to be connected within 30 minutes.

If the alert interval has not yet elapsed (factor 810) and thenon-connectable interval is still running (factor 825), the ID nodesimply stays in state 805. However, if the alert interval has notelapsed (factor 810) and the non-connectable interval elapses (factor825), the ID node will enter a mode where it wants to try to connect toanother node for a period of time (e.g., a 1 minute connectableinterval) and will move to the ID Node General Advertising state 830 inthe exemplary advertising cycle of FIG. 8. In state 830, as long as theconnectable interval is running, the ID node will stay in this statewhere it is connectable to another node and will receive SCAN_REQ typesof requests from other nodes in response to the advertising packets theID node is broadcasting. However, when the connectable interval (e.g.,the 1 min period) elapses or expires (factor 835), the ID node returnsback to the Non-connectable Advertising state 805 for either the nexttime the non-connectable interval elapses (and the ID node again triesto connect in state 830) or the alert interval finally elapses (and theID node finds itself in a situation where it has not connected toanother node despite its efforts to connect in state 830).

When the alert interval finally elapses (factor 810), the ID node movesto the ID Node Discoverable Advertising state 815. Here, the ID node isnot yet connectable but will receive a SCAN_REQ type of request fromother nodes in response to advertising packets the ID node isbroadcasting. In this state 815, the exemplary ID node may alter itsstatus flag to indicate and reflect that its alert interval has expiredand that the node is now no longer in normal operation. In other words,the ID node may change the status flag to a type of alert status beingbroadcasted to indicate the ID node urgently needs to connect withanother node. For example, the status flag of the advertising packetbroadcast by the ID node may be changed to one of the higher AlertLevels depending on whether the node needs to upload data (e.g., AlertLevel 3 status) or synchronize timer or other data with another node(e.g., Synchronize status). With this change in status flag, and the IDnode in state 815 broadcasting, the ID node awaits to receive a requestfrom another node that has received the broadcast and requested moreinformation via a SCAN_REQ message (factor 820) sent to the ID node fromthat other node. Once a SCAN_REQ message has been received by the IDnode (factor 820), the ID node that went into the alert mode because ithad not connected with another node within the alert interval canconnect with that other node, upload or share data as needed, and thenshift back to state 805 and restart the alert interval andnon-connectable intervals.

Master Node to ID Node Association Example

Advertising (broadcasting) and scanning (listening) are ways nodes maycommunicate during association operations. FIGS. 9-12 provide examplesof how network elements of a wireless node network (e.g., ID nodes,master nodes, and a server) may communicate and operate when connectingand associating as part of several exemplary wireless node networkoperations.

FIG. 9 is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary master-to-ID node association in accordancewith an embodiment. Referring now to FIG. 9, exemplary master node M1910 a is illustrated within communication range of exemplary ID node A920 a. Master node M1 910 a also has a communication path back to server900. As shown, master node M1 910 a is in a scanning or listening mode(e.g., indicated by the “M1_(scan)” label) while ID node A 920 a is inan advertising or broadcasting mode (e.g., indicated by the “A_(adv)”label). In this example, M1 master node 910 a has captured the addressof ID node A 920 a through A's advertising of at least one advertisingdata packet, and has reported it to the server 900. In this manner, thecapturing and reporting operations effectively create a “passive”association between the nodes and proximity-based custodial control.Such an association may be recorded in the server, such as server 900,as part of association data, such as association data 540.

In another embodiment, passive association between a master node and IDnode may be extended to an “active” association or connection. Forexample, with reference to the embodiment shown in FIG. 9, server 900may instruct master node M1 910 a to associate, connect, or otherwisepair with ID node A 920 a, and forwards the required securityinformation (e.g., PIN credentials, security certificates, keys) tomaster node M1 910 a. Depending on the advertising state of ID node A920 a, ID node A 910 a may only be visible (discoverable) but notconnectable. In such a situation, the master node M1 910 a must waituntil ID node A 920 a is in a connectable state (e.g., the ID NodeGeneral Advertising state) and can be paired. As discussed above withreference to FIG. 8, each ID node has a certain time window during eachtime period where it can be paired or connected.

In this example, when the ID node A 920 a is successfully paired withmaster node M1 910 a, ID node A 920 a may no longer advertise itsaddress. By default, only an unassociated device will advertise itsaddress. A paired or associated node will only advertise its address ifinstructed to do so.

ID Node to ID Node Association Example

In various embodiments, an ID node may associate with or connect toother ID nodes. FIG. 10 is a diagram illustrating exemplary componentsof a wireless node network during an exemplary ID-to-ID node associationin accordance with an embodiment of the invention. Referring now to FIG.10, exemplary master node M1 910 a, ID node A 920 a, and server 900 aresimilarly disposed as shown in FIG. 9, but with the addition of ID nodeB 920 b, which is within communication range of ID node A 920 a. In thisexample, ID node A 920 a is running in query (scan) mode (e.g.,A_(scan)) listening for ID node B 920 b. When ID node A 910 a detects IDnode B 920 b advertising (e.g., B_(adv)) with one or more advertisingdata packets as part of an advertised message from ID node B 920 b, IDnode A 920 a identifies a status flag from the message indicating IDnode B 920 b has, for example, data (e.g., sensor data 350) for upload.As a result, ID node A 920 a logs the scan result (e.g., as a type ofassociation data 340) and, when next connected to master node M1 910 a,ID node A 920 a uploads the captured scan log information to the server900. In this manner, the ID node scanning, capturing, and reportingoperations effectively create a “passive” association between thedifferent ID nodes. Such a passive association may be recorded in theserver 900 as part of association data 540.

In another embodiment, passive association between two ID nodes may beextended to an “active” association or connection. For example, withreference to the embodiment shown in FIG. 10, based upon the capturedstatus flag and uploaded information about ID node B 920 b under thatmode, the server 900 may issue a request to ID node A 920 a throughmaster node M1 910 a to actively connect or pair with ID node B 920 bfor the purpose of downloading information from ID node B 920 b. In oneexample, security credentials that authorize the active connectionbetween ID node A 920 a and ID node B 920 b are downloaded to ID node A920 a from master node M1 910 a, which received them from server 900. Inanother example, the requisite security credentials may have beenpre-staged at ID node A 920 a. And rather than rely upon an ID node toID node connection, master node M1 may have connected directly with IDnode B 920 b if M1 was within communication range of ID node B 920 b.

Information Query ID Node to Master Node Example

An exemplary ID Node may also issue queries to other nodes, both masternodes and ID nodes. FIG. 11 is a diagram illustrating exemplarycomponents of a wireless node network during an exemplary ID-to-masternode query in accordance with an embodiment of the invention. Referringnow to FIG. 11, a similar group of nodes as shown in FIG. 9 appears,except that exemplary master node M1 910 a is in an advertising orbroadcasting mode (e.g., M1_(adv) while ID node A 920 a is in a scanningmode (e.g., A_(scan)). In this configuration, ID node A 920 a may querymaster node M1 910 a for information. In one embodiment, the query maybe initiated through the ID node setting its status flag. The requestedinformation may be information to be shared, such as a current time,location, or environmental information held by the master node M1 910 a.

In a passive association example, ID node A 920 a in A_(scan) mode mayhave captured the address of master node M1 910 a. However, since an IDnode cannot directly connect to the server 900 to request pairingsecurity credentials (e.g., security pin information that authorizes anactive connection between ID node A 920 a and master node M1 910 a), apassive association and corresponding pairing will have been initiatedfrom the master node. In another example, it may be possible for ID nodeA 920 a to have the pairing credentials stored as security data 335 froma previous connection. This would allow ID node A 920 a then to initiatethe active association with master node M1 910 a after a passiveassociation.

Alert Level Advertising Example

As previously noted, a node may enter an alert stage or level in one ormore embodiments. For example, if a node has not received anacknowledgement from a master node for an advertising packet within aset period (e.g., an Alert Interval as described in some embodiments),the node will enter a particular alert stage for more specializedadvertising so that it may be “found” or pass along information. FIG. 12is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary alert advertising mode in accordance with anembodiment of the invention. Referring now to FIG. 12, a similar groupof nodes as shown in FIG. 9 appears, with the addition of another masternode (master node M2 910 b) and another ID node (ID node B 920 b).Exemplary ID node A 920 a is in an advertising or broadcasting mode(e.g., A_(adv)) while nodes M1, M2, and B are each in scanning mode(e.g., M1_(scan), M2_(scan), and B_(scan)). In this example andconfiguration as shown in FIG. 12, the status flag in an advertisingmessage from ID node A 920 a has been set to a particular alert level(e.g., Alert Level 2) in the header of the message, requesting anynearby master node to acknowledge it. In one example, this mode may beentered if ID node A 920 a has not connected with another node for a setperiod or time. In another example, ID node A 920 a may enter thisspecialized advertising mode upon received instructions (e.g., fromserver 900 or another nearby node) or a triggered condition (other thantime), such as when a sensor input (such as light) is detected orotherwise registered and the node issues continuous updates of itsaddress as a security feature. The ID node A 920 a set at this alertlevel and in this specialized advertising mode is thus set in an activepairing mode, waiting for pairing credentials.

From a passive association perspective, any node in scanning mode canpassively associate with such an advertising node (e.g., ID node A 920 ain this alert mode). Thus, in an embodiment, the Alert Level 2 statusflag in the advertising header broadcast by ID node A 920 a indicatesthat urgent and active intervention is requested, rather than merelypassively associate without an active connection.

From an active association perspective, any node that uploads thespecial advertising header of ID node A 920 a may be forwarded thesecurity credentials from the server 900. This would allow for the nodereceiving such credentials to actively associate or pair with ID node A920 a.

While FIG. 8 provides examples of how a node may advertise, and FIGS.9-12 provide examples of how different exemplary devices (e.g., IDnodes, master nodes, and a server) may advertise and associate indifferent ways, FIGS. 22A-C provide a progressive set of illustrationsthat expand upon how associating and disassociating may be appliedwithin an exemplary wireless node network. More specifically, FIGS.22A-C show how associations and disassociations may occur when anexemplary ID node is tracked and managed by a server and differentmaster nodes as the ID node moves through an exemplary transit path inaccordance with an exemplary embodiment of the invention.

Referring now to FIG. 22A, a structure 2200 is shown having an entry andexit point. In one example, the structure 2200 may be a corridor oranother part of a building or facility. In another example, structure2200 may be a conveyor system that transports an item and its ID nodefrom the entry point to the exit point. Master node M1 2210 a is locatednear the entry point of structure 2200 while master node M2 2210 b islocated near the exit point. Those skilled in the art will appreciatethat other master nodes may be disposed at additional points instructure 2200, but are not shown for sake of convenience and tosimplify the association hand-off explanation that follows. Server 100is operatively connected to each of master node M1 2210 a and masternode M2 2210 b via network 105.

In one embodiment, server 100 has access to context data 560 related tothe structure 2200, such as layout data 585 on dimensions and materialsmaking up structure 2200. Context data 560 may include historic data 575on how an ID node has operated and successfully been tracked as ittraverses structure 2200 from the entry point to the exist point. Forexample, server 100 may have context data indicating structure 2200 is aconveyor that can transport an item and its ID node from the entry pointto the exit point over a distance of 800 feet. The context data mayfurther indicate typical items are moved at a certain speed on theconveyor of structure 2200 and a nominal time from the entry point tothe exit point may be about 5 minutes. Thus, the server 100 has accessto context data about the environment within with an ID node isoperating and may leverage this to better and more accurately manage theID node.

In FIG. 22A, ID node A 2220 a is shown entering the structure 2200 atthe entry point. Here, ID node A 2220 a may be advertising in hopes ofconnecting with a master node as it enters structure 2200 with, forexample, a non-connectable interval of 10 seconds with a connectableinterval of 5 seconds. In this example, the server 100 knows that IDnode A 2220 a is located near the entry point and anticipates that IDnode A 2220 a should be coming near to master node M1 2210 a at theentry point. Thus, server 100 may set the connectable andnon-connectable intervals accordingly so as to provide a sufficientopportunity for ID node A 2220 a to connect to the next master nodealong the predicted path of the ID node and in accordance with the speedof travel.

Additionally, server 100 may set the alert interval to 1 minute in thiscontext. Here, if ID node A 2220 a is not connected to another nodewithin 1 minute, ID node A 2220 a may broadcast or advertise with amessage having a changed status flag that indicates an alert status sothat ID node A 2220 a can connect to a broader range of other nodes thatsee it is urgent for ID node A 2220 a to connect and, essentially, befound. Depending on the context (e.g., the type of conveyor, the speedof the conveyor, the density of nodes near the entry point, etc.), thoseskilled in the art will appreciate that the server 100 can adjust theadvertising cycle intervals to better accommodate the ID node's currentenvironment.

When master node M1 2210 a is scanning (listening), it may initiallydetect an advertising packet from ID node A 2220 a during node A'snon-connectable interval. But when ID node A 2220 a changes advertisingstates and broadcasts as a connectable node in the general advertisingstate (i.e., during the connectable interval), master node M1 2210 a mayrespond with a SCAN_REQ that acknowledge receipt of the broadcastedmessage and asks for further information from ID node A 2220 a. Masternode M1 2210 a receives the requested information from ID node A 2220 a,and then communicates with the server 100 to notify the server of itspassive association with ID node A 2220 a. Server 100 determines ifactive association is desired, and may authorize the active associationbetween master node M1 2210 a and ID node A 2220 a by sending securitycredentials to master node M1 2210 a, which allow the nodes to securelyconnect and share information. And master node M1 2210 a may determinethe location of ID node A 2220 a (or server 100 may do so by directingmaster node M1 and/or ID node A), and provide the location of ID node A2220 a to server 100. Thus, server 100 is able to manage and track thelocation of ID node A 2220 a as it enters structure 2220 via at leastassociation.

In FIG. 22B, ID node A 2220 a has traversed down part of the transitpath through structure 2200 while remaining associated with master nodeM1 2210 a. However, at some point master node M1 2210 a and ID node A2220 a are disassociated at the direction of server 100 (or when theycan no longer communicate). In one example where ID node A 2220 a is onthe conveyor within structure 2200, server 100 may instruct ID node A2220 a to go to a low power mode for a particular period of time inorder to, for example, conserve ID node power. In another example, thelow power mode may also provide better location accuracy. As the server100 has access to the context data, the server 100 may know that ID nodeA 2220 a was associated with master node M1 2210 a near the entry pointat a given time, and determine that ID node A 2220 a will not be nearthe exit point until the end of the particular period of time. With theID node A 2220 a programmed this way, once the particular periodelapses, the ID node A 2220 a should be near the exit point and mayagain be placed into a normal operation mode so that it can seek toconnect with master node M2 2210 b.

Similar to the association process discussed with respect to ID node Aand master node M1, ID node A 2220 a and master node M2 2210 b may beassociated as ID node A 2220 a approaches master node M2 2210 b near theexit point. Once connected, the node locations and association data areupdated on the server 100. And as ID node A 2220 a continues to movethrough structure 2200, ID node A 2200 a may arrive at the exit point asshown in FIG. 22C, where the node locations and association data areupdated once again on the server 100.

Those skilled in the art will appreciate how such principles may beapplied to further movements of an ID node as it is handed off (e.g.,via active/passive associations and disassociations) between othermaster nodes and keeping track of these associations and node locationson the server 100. Additionally, as server 100 tracks and monitorsassociations, disassociations, and contextual environmental operations,server 100 essentially learns how to better use context informationbetter track nodes, manage power used by ID nodes, and enhance accuracyfor locations.

Those skilled in the art will also appreciate the general tradeoff witha level of RF power level and accuracy of location. If a node's RF powerlevel is set high, it may advertise and connect with other nodes alonger distance away. But at such a high power level setting, theability for the system to discriminate between and locate differentnodes may be a challenge.

Association Management within a Wireless Node Network

As explained above in general, management of nodes may rely uponassociations created and tracked between nodes. In some embodiments, theassociation relied upon may be an active association where the serverexpressly authorizes an active connection between nodes. In otherembodiments, the association relied upon may be a passive associationwhere the master node (a type of managing node) is associated with theother node, but not actively connected to the other node. By virtue ofthe passive association, the server may be able to keep track of andmanage the other node without requiring an active association. Thus,those skilled in the art will appreciate that in still otherembodiments, associations relied upon by the server for managing awireless node network may include both active and passive associationsand may be generally authenticated or, more specially, authorize asecure connection that has a degree of protection for the connection andcommunications using that connection.

FIGS. 23-25 provide flow diagrams of exemplary methods for associationmanagement of a wireless node network having at least a plurality ofnodes and a server in accordance with different embodiments of thepresent invention involving active and passive association examples.Those skilled in the art will appreciate that each of these exemplarymethods for association management of a wireless node network may beimplemented by instructions stored on a non-transitory computer-readablemedium, which when executed perform the steps of the respective methodsdescribed below (e.g., methods 2300, 2400, and 2500) and the describedvariations of those methods.

Referring now to FIG. 23, method 2300 begins by identifying a first nodeas a potential for actively associating with a second node at step 2305.In one example, identifying the nodes for association may involvereviewing a message sent by the first node to determine statusinformation related to the first node, and analyzing the statusinformation to determine whether the first node should be associatedwith the second node. In a further example, the status information maycomprise one of a plurality of different status levels indicatingwhether the first node is requesting a connection to the second nodewhen at that particular status level.

Next, an association request is transmitted to the server in step 2310.In one example, the association request may identify the first node andsecond node to be associated and may request transmission of one or moreappropriate security credentials (e.g., PIN credentials, securitycertificates, keys, and the like) that may be used by the nodes toenable the first and second node to securely connect and share data aspart of associating. An embodiment may request only one credential as anauthorization credential from the server. Other embodiments may use twocredentials where one may be later uses as a credential with which toreply to challenges. For example, if an ID node is challenged, the IDnode may send a reply authorization credential so that the master nodecan confirm the response and supply the ID node with the appropriatesecurity credential for the authorized association. In some cases, an IDnode may have been supplied with such a reply authorization credential(also generally referred to as a key) by the server.

At step 2315, the second node receives a permissive response from theserver related to the association request. In an example, the permissiveresponse may include receiving a first authorization credential and asecond authorization credential from the server (which may be stored onthe nodes). As such, the first authorization credential and the secondauthorization credential may be created by the server as a type ofsecurity data, and may be provided to authorize connecting the firstnode and the second node and securely sharing information between thefirst node and the second node.

With this authorization from the server, the first node and second nodemay be associated at step 2320. In one example, the method 2300 mayassociate the nodes by establishing an authorized connection from thesecond node to the first node based upon the authorization credential.And the method 2300 may securely provide shared data between the firstnode and the second node according to a profile established by theserver after the first and second nodes are associated.

In an embodiment, the method 2300 may also comprise having the secondnode gaining responsibility for a task after the second node isassociated with the first node when responsibility for the task waspreviously with the first node. For example, when the second node ispowered by an external power source and the first node is powered by abattery, this may advantageously shift the responsibility to a node thatis better suited to perform the task (e.g., has more power available orhas a power source that does not need recharging or replacing).

FIG. 24 is a flow diagram illustrating another example method forassociation management of a wireless node network in accordance with anembodiment of the invention from the perspective of the server.Referring now to FIG. 24, method 2400 begins with the server receivingan association request sent from a second of the nodes at step 2405. Theassociation request asks for permission to associate a first of thenodes to the second node.

At step 2410, the server determines a location (actual or relative) ofthe first node and second node. In one embodiment, the server mayreceive location data for the second node. For example, when the secondnode is a master node, the location data for the second node may be GPScoordinates for the current location of the master node, which providesthis to the server. And in an embodiment, the server may determine alocation of the first node using at least one of a plurality of locationmethods available to the server for locating the first node, such asthose discussed in detail above (or a combination of such methods sothat a more refined location of the first node is determined).

At step 2415, the server determines if associating the first node to thesecond node is desired based at least upon the location of the firstnode and the location of the second node. In one embodiment, it may bedetermined if associating is desired by determining if associating thefirst node to the second node is anticipated based upon context data. Inanother embodiment, it may be determined if associating is desired byidentifying a current mode of filtering that limits potential nodes tobe associated, and granting the permission to associate the first nodeto the second node only if the current mode of filtering allows thefirst node to be associated with the second node. For example, this mayinvolve granting the permission only if the current mode of filteringdefines that the second node is within a locational range of the firstnode consistent with the current mode of filtering. This may be definedby a particular filtering mode, such as a local, regional, or globalfiltering mode that operates to restrict nodes that may associate withother nodes. As such, the method may alter the current mode of filteringto another mode of filtering that allows the first node to be associatedwith the second node as a sort of override of the current filtering mode(e.g., depending upon an alert status of the first node).

At step 2420, the server records new association data if it is desiredto associate the first node with the second node at step 2420. At step2425, the server transmits a response to the second node granting thepermission to associate the first node to the second node. In anembodiment, the server may first generate an authorization credentialthat authorizes connecting the first node and the second node andsharing information between the first node and the second node. This maybe by looking up the credential information or by going through aprocess to create specific an authorization credential that allows thetwo nodes to actively pair and share data. With the authorizationcredential, the server may transmit them as the response.

In another example, the server may have pre-staged an authorizationcredential related to the second node and a third node if the serveranticipates the second node will disassociate with the first node andlater request to associate with the third node. For example, this may bedone if the context indicates the second node (e.g., a master node) maybe placed in a container and need to connect with the third node in thefuture when the second node may lose its connection to the server.

Method 2400 may also include the server receiving shared data from thesecond node. The shared data may originate from the first node or mayhave parts that originate from both the first and second nodes. Forexample, the second node may have received the permission to associate,and actively paired with the first node in a secure manner. The firstnode may have indicated it has data to upload (e.g., sensor data), andthe second node may receive the data from the first node. Subsequent tothat sharing, the second node may upload the shared sensor data from thefirst node by transmitting it to the server.

The method may further comprise instructing the second node to take overresponsibility for a task previously performed by the first node afterthe second node is associated with the first node. For example, when thesecond node is powered by an external power source and the first node ispowered by a battery, the responsibility for certain tasks may be takenover by the node with a more robust power supply (e.g., the node poweredby an external power source).

In more detail, the responsibility for certain tasks may be established,tracked and changed with a programmable profile. For example, in oneembodiment, the server may establish a profile for how long the taskresponsibility would change. In some cases, the profile may define aperiod of time for how long a node having this profile would haveresponsibility for a certain task before it would revert back to adefault node. In another example, a node (such as a master node) mayhave a default condition trigger (like a low power situation or when itcannot communicate with the server) that can override such a profile sothat it does not take on more responsibilities under particularconditions.

Furthermore, an embodiment may have the master node deciding what othernode may take on responsibility for certain tasks. This may be helpfulin situations where access to the server may be limited (e.g., anairborne environment). However, managing such a profile may be moreeasily accomplished in other embodiments with easier access to moretypes of context data on the server level.

In an embodiment that implements association management as a system,such an exemplary system for association management of a wireless nodenetwork may comprise a first node, a second node, and a server. Thesecond node includes a node processing unit, a node volatile memorycoupled to the node processing unit, a first communication interfacecoupled to the node processing unit, and a second communicationinterface coupled to the node processing unit. The first communicationinterface provides a short-range communication path between the firstnode and the second node and the second communication interface providesa longer range communication path between the second node and theserver.

The server includes a server processing unit, a server volatile memorycoupled to the processing unit, and a third communication interface thatprovides a longer range communication path between the server and thesecond communication interface of the second node.

The node volatile memory maintains at least a first program code section(e.g., master control and management code 425 or parts thereof) whilethe server volatile memory maintains at least a second program codesection (e.g., server control and management code 525 or parts thereof).

When executing the first program code section resident in the nodevolatile memory, the node processing unit of the second node isoperative to identify the first node as a potential for associating withthe second node, transmit an association request over the secondcommunication interface to the server, receive an association response(having at least authorization information generated by the server) overthe second communication interface from the server, provide theauthorization information to the first node, and associate the firstnode and the second node.

In one example, the node processing unit may be further operative toreview status information related to the first node to determine whetherthe first node desires association with the second node. In anotherexample, the node processing unit may be further operative to securelyprovide shared data between the first and second node after the firstand second node are associated and in accordance with a sharing profileprovided by the server. The sharing profile may define types ofinformation to be securely shared between particular nodes.

When executing the second program code section resident in the servervolatile memory, the server processing unit is operative to determine alocation of the first node and second node, determine if associating thefirst node to the second node is desired based at least upon thelocation of the first node and the location of the second node, storenew association data in the server volatile memory if it is desired toassociate the first node with the second node, and transmit theauthorization response to the second node granting the permission toassociate the first node to the second node.

In one embodiment, the second node in the system may take overresponsibility of a task previously handled by the first node after thesecond node is successfully associated with the first node. For example,when the second node is powered by an external power source and thefirst node is powered by a battery, the system may be more effectivelyand efficiently managed by reassigning a task (especially a task thatinvolves a significant expenditure of power, a series of operations overa significant period of time, or both) to another node, such as thesecond node, which has more power available than the first node.

In another embodiment, the server processing unit may be furtheroperative to set a current mode of filtering that limits potential nodesto be associated, and grant the permission to associate the first nodeto the second node only if the current mode of filtering allows thefirst node to be associated with the second node. In a furtherembodiment, the server processing unit may be further operative to alter(e.g., override) the current mode of filtering to a different mode offiltering. In this way, the server may adapt how nodes are managed andallow the first node to be associated with the second node if it isdesired, such as then the first node is in an alert status level andurgently is requesting connection to a larger group of nodes thanpermitted under the current mode of filtering.

While the exemplary methods illustrated in FIGS. 23 and 24 focus onactive associations, FIG. 25 is a flow diagram illustrating an examplemethod for association management of a wireless node network having atleast a plurality of nodes and a server in accordance with anembodiment, but from the perspective of a node that is to be passivelyassociated with another node. Referring now to FIG. 25, method 2500begins with a second of the nodes receiving a message broadcasted from afirst of the nodes at step 2505. At step 2510, the second node capturesan address of the first node from the message. At step 2515, the firstnode and the second node are associated by storing the captured addressof the first node and an address of the second node as association datain a memory of the second node. At step 2520, the second node transmitsthe association data to the server.

At some point, the server may be updated by the second node with updatedassociation data when the second node does not receive an additionalmessage broadcast from the first node. For example, the second node andthe first node may stay associated and securely connected for a periodof time, but eventually the first node may move such that the connectionis no longer viable or the first node may move closer to another nodealong the anticipated path it is traveling (e.g., an anticipatedshipping path along a conveyor within a structure from an entry point ofthe structure but now closer to an exit point of the structure). As thefirst node travels on the conveyor, it may get closer to another nodenear the exit point and is better managed by an association with thatother node near the exit point. Thus, the updated association datareflects that the first node is disassociated from the second node.

Method 2500 may further include having the second node determining alocation of the first node, and updating the server with a currentlocation of the second node and the determined location of the firstnode. Additionally, method 2500 may include receiving locationinformation from the server that defines a refined location of the firstnode.

In an embodiment that implements passive association management as amanaging node (e.g., a master node) in a wireless node having at leastanother node and a server, such an exemplary managing node comprises aprocessing unit, a first and second communication interface each coupledto the processing unit, a volatile memory coupled to the processingunit, and a memory storage coupled to the processing unit. The firstcommunication interface provides a first communication path to the othernode, can receive a message broadcast from the other node, and providethe message to the processing unit. The second communication interfaceproviding a second communication path to the server.

The memory storage may maintain at least a node association managermodule as program code to be executed by the processing unit. When theprocessing unit loads the module into volatile memory and executesinstructions of the module, the processing unit is operative to receivethe message from the first communication interface, capture an addressof the another node from the message, store the captured address of theanother node and an address of the managing node as part of associationdata in the memory storage, and transmit the association data to theserver through the second communication interface.

In one example, the memory storage also maintains a location managermodule and, when the processing unit also loads the location managermodule into volatile memory and executes instructions of that module,the processing unit is operative to determine a location of the othernode, determine a current location of the managing node (e.g., via GPSlocation signals), and update the server with the current location ofthe managing node and the determined location of the other node.

The managing node may be further operative to update the server withupdated association data when the first communication interface does notreceive an additional message broadcast from the other node. The updatedassociation data may reflect that the other node is disassociated fromthe managing node.

Context Management within a Wireless Node Network

As explained above in general, management of nodes may rely upon thecontextual environment of the nodes. As shown in FIG. 5, server 100 hasaccess to a wide variety of different context data 560. Context data,such as data 560, may include a wide variety of data that generallyrelates to the environment in which the nodes are operating and may beused to advantageously provide enhanced node management capabilities inaccordance with embodiments of the present invention. As such, the useof such context data provides a data foundation in an embodiment so thatthe server may better and more efficiently implement management tasksrelated to nodes in the network, and adjust such tasks to account forrelevant context data as nodes move within the network (e.g., as an IDnode moves with an item being shipped along an anticipated or predictedtransit path from an origin to a destination). For example, the servertake advantage of its ability to rely upon relevant context data toadvantageously alter how it instructs a node operate, how it associatesa node with the another node, how it can better locate a node, and howit can more efficiently track and respond to requests to report thelocation of the node.

FIG. 26 is a flow diagram illustrating an exemplary method for contextmanagement of a wireless node network in accordance with an embodimentof the invention. Referring now to FIG. 26, method 2600 begins at step2605 by identifying, by the server, at least one of the nodes. In oneexample, such as that shown in FIG. 22a , server 100 may identify IDnode A 2220 a as part of communications received from master node M12210 a. At step 2610, the server determines context data that relates toan operating environment of the identified node as the identified nodemoves within the operating environment.

In one embodiment, the context data may include one or more types ofdata, such as scan data, historic data, shipment data, RF data, andlayout data. For the example shown in FIG. 22a , server 100 may accesscontext data 560 (which may be kept in context database 565) todetermine parts of the context data 560 that relate to the operatingenvironment of ID node A 2220 a. Such context data 560 may include, inthis example, shipment data that relates the item being shipped that isconnected to ID node A 2220 a, scan data for when the item connected toID node A 2220 a was scanned upon entering structure 2200, historic datafor how long it takes a node to traverse the conveyor located withinstructure 2200, and layout data on dimensions of structure 220. Thoseskilled in the art will appreciate that context data may includeoperational environment information created within the wireless nodenetwork or created by a third party (e.g., weather information relatedto the operating environment of ID node A 2220 a).

While the server determines context data that relates to an operatingenvironment of the identified node in one embodiment, such a current oranticipated operating environment for a node in a more detailedembodiment may include one or more types of environments. For example,the current or anticipated operating environment for a node may includean electronic communication environment, a physical environment of ananticipated path along with a node moves, a conveyance environmentrelated to how a node moves, and a density environment related to thedensity of nodes within an area near a particular node identified by theserver.

Back at step 2610, the determining step may involve determining thecontext data that relates to an anticipated operating environment of theidentified node as the identified node moves in a predicted path towardsa location of another node. In another example, the determining step mayinvolve determining the context data that relates to the anticipatedoperating environment of the identified node and an anticipatedoperating environment of the another node as the identified node movesin the predicted path towards the another node for an expectedassociation with the another node

At step 2615, the server performs a management task related to theidentified node with an adjustment made to account for the determinedcontext data. When the determined context data (such as RF signaldegradation information) indicates that no adjustment is actually neededwhen performing the task, no adjustment is made given the determinedcontext data. Thus, those skilled in the art will appreciate that anadjustment may be made when needed contextually and is not required atall times.

In one embodiment, performing the management task may comprise generallyinstructing the identified node to alter its operation based upon thedetermined context data. For example, server 100 may perform themanagement task of instructing ID node A 2220 a to change itsconnectable and non-connectable intervals as it approaches master nodeM1 (which server 100 knows from context data, such as scan datagenerated when node A entered structure 2200). Thus, in this example,server 100 is able to leverage enhanced visibility of ID node A 2220 abased upon context data and advantageously alter the operation of node Ato increase the node's chance of successfully associating with masternode M1 2210 a.

In other embodiment, performing the management task may compriseassociating the identified node with another node with the adjustmentmade to alter an associating parameter based upon the determined contextdata. In other words, context data may be helpful as part of associatingnodes. In one example, the associating parameter may include at leastone altered timing interval related to associating the identified nodewith the other node, such as an alert interval or connectable interval.These intervals are parameters that may be altered as part ofadjustments made when a server associates two nodes and, for example,sets the intervals to more appropriate time durations in order toenhance the chance and opportunity the nodes have to actively pair andsecurely share data as needed.

In yet another embodiment, performing the management task may compriselocating the identified node with an adjustment made to a power settingbased upon the determined context data. In one example, the powersetting adjustment is done to a master node in direct communication withthe server. In another example, the power setting adjustment may be doneto an ID node, which is passed this operational adjustment informationfrom another node. In one embodiment, the power setting itself maycomprise an output power level adjusted to account for an adversecondition in the operating environment of the identified node (e.g., amaster node with an adjusted RF output signal level). The adversecondition may be, for example, an adverse RF communication environmentwhere structure attenuates or otherwise impedes normal RFcommunications. In another example, the adverse condition may be ahighly dense population of nodes close to the identified node.

In more detail, the output power level may be adjusted to account for ashielding condition in the operating environment of the first node. Sucha shielding condition may be caused, for example, by one or more ofpackaging, package contents, proximate package, proximate packagecontents, and physical infrastructure in the operating environment ofthe first node. For example, if the identified node is located near ametal container, it is operating in an adverse RF communicationsenvironment where it may have its output power level increased based onthis context data in order to better deal with the adverse shieldingcondition.

In still another embodiment, performing the management task may compriseproviding the location of the identified node in response to a requestreceived by the server related to a status of the identified node. Forexample, if server 100 receives a request from user access device 205about the status of ID node A 2220 a, server 100 is able to provide thelocation of node A as being within structure 2200, but refined as beingclose to the entry of the structure given the adjustment to account forcontextual data, such as scan data related to the item being shippedwith node A 2220 a.

Those skilled in the art will appreciate that method 2600 as disclosedand explained above in various embodiments may be implemented on aserver, such as server 100 illustrated in FIGS. 5 and 22A, running oneor more parts of server control and management code 525 (e.g., thecontext based node manager). Such code may be stored on a non-transitorycomputer-readable medium such as memory storage 515 on server 100. Thus,when executing code 525, the server's processing unit 500 may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 2600 and variations of that method.

Node Location Determination Methodologies

As part of managing and operating a wireless node network in accordancewith one or more embodiments of the invention, such as tracking ID nodeA 2220 a in FIGS. 22A-C, determining a node's location is performed. Asexplained above, an exemplary ID node may be directly or indirectlydependent on a master node to determine its location. In the embodimentsdiscussed and described herein, a location of a node may generallyencompass a current or past location. For example, an embodiment thatdetermines a node's location may be a current location if the node isnot moving, but may necessarily determine the location as a pastlocation should the node be in a state of motion.

Likewise, the term location alone may include a position with varyingdegrees of precision. For example, a location may encompass an actualposition with defined coordinates in three-dimensional space, but use ofthe term location may also include merely a relative position. Thus, theterm location is intended to have a general meaning unless otherwiseexpressly limited to a more specific type of location.

Determining node location may done by a master node alone, the serveralone, or the master node working together with the server. And on suchdevices, embodiments may use one or more methodologies to determine anode's location and further refine the location. Such examplemethodologies may include, but are not limited to, determining nodelocation may relate to controlling an RF characteristic of a node (e.g.,an RF output signal level and/or RF receiver sensitivity level),determining relative proximity, considering association information,considering location adjustments for context information and an RFenvironment, chaining triangulation, as well as hierarchical andadaptive methods that combine various location methodologies. A moredetailed description of these exemplary node location determinationtechniques is provided below.

Location Through Proximity

In one embodiment, a signal strength measurement between two or morenodes may be used to determine the proximity of the nodes. If neithernode's actual location is known, one embodiment may infer a locationrelationship of the two nodes through proximity.

Proximity when Varying Power Characteristics

For example, an exemplary method of determining a node's location in awireless node network of nodes may involve varying a node's powercharacteristic, such as the output power of one of the nodes. Generallyand as explained with reference to FIG. 13, the power characteristic maybe varied to identify closer ones of the nodes to the node broadcasting.The node broadcasting may transmit one or a series of signals whileother nodes may report receiving one or more of the signals. Those othernodes that receive at least one signal broadcast from the transmittingnode may be deemed part of a close group of nodes. And as the powercharacteristic is varied (increased or decreased or both), a closestgroup of nodes (or single node) may be identified as the smallest groupof nodes of those that receive at least one signal from the broadcastingnode. Accordingly, while not absolute, a type of location for thebroadcasting node may be determined based on the closest one or group ofnodes. This may be repeated for neighboring nodes to yield a set ofclosest node information for each of the nodes. In more detail, anexemplary set of closest node information for each of the nodes mayinclude which nodes are closest (via the lowest power characteristic)and more robustly supplement this information with which other nodes areincrementally further away (via increasingly larger powercharacteristics). Thus, the set of closest node information provides thebasis for a determination of how close the nodes in the network are toeach other, which provides a type of location determination for eachnode.

Additionally, context data may be referenced in certain embodiments tofurther enhance determining how close the nodes are to each other. Forexample, combining the set of closest node information with contextdata, such as scan information that registers when an item changescustodial control in a delivery system, may further refine how todetermine the location of the nodes. Scan and other context informationwill help determine if one or more of the nodes, for example, are knownto be in the same container, vehicle or moving on a belt together. Thus,this type of context data may be integrated into a further step ofrefining how close the nodes are to each other based upon the contextdata.

In general, a location of a node based upon proximity may be determinedwhen a power characteristic of nodes is changed or varied in a wirelessnode network. FIG. 28 is a flow diagram illustrating an exemplary methodfor location determination by varying a power characteristic of nodes ina wireless node network in accordance with an embodiment of theinvention. Referring now to FIG. 28, method 2800 begins by at step 2805by instructing a first of the nodes to vary the power characteristic forone or more signals broadcast by the first node. In a more detailedembodiment, such an instruction may cause the first node, for example,to incrementally decrease or incrementally increase the powercharacteristic (such as an output power level) between values.

At step 2810, method 2800 continues by identifying a first group ofother nodes in the wireless node network that are near the first nodebased upon those of the other nodes that received at least one of thesignals broadcast by the first node as the first node varies the powercharacteristic. In a further embodiment, step 2810 may incrementallyidentifying which of the first group of other nodes are receiving atleast one of the broadcast signals as the first node incrementallyvaries the output power level of the signals broadcast. Theincrementally identified nodes may be deemed a set of increasingly closenodes to the first node.

At step 2815, method 2800 continues by identifying a closest one or moreof the other nodes as a smallest group of the other nodes that receivedat least one of the one or more signals broadcast by the first node asthe first node varies the power characteristic.

At step 2820, method 2800 concludes by determining a location of thefirst node based upon the closest one or more of the other nodes. Thus,as the power characteristic is varied, the group of nodes that havereceived at least one of the signals broadcast by the first node maychange and the smallest such group being a closest group of nodes (evenif just one node) to the first node. In a more detailed embodiment, step2820 may comprise determining the location of the first node based uponthe closest one or more of the other nodes and the set of increasinglyclose nodes to the first node as the set of increasingly close nodesprovides more detailed proximity information for a refined locationdetermination.

For example, referring to FIG. 14, the set of increasingly close nodesto the ID node F 920 f may include node M3 as being farthest away and M1being closer than M3. When the power characteristic of ID node Fincrementally decreases, and its output power level changes from P1 toP2, M3 can no longer receive the signal, but M1 and M2 still do. And asthe power characteristic of ID node F continues to incrementallydecrease, and its output power level is changed from P2 to P3, M1 can nolonger receive the signal, but only M2 does as the last of the nodesclosest to ID node F. Thus, in this example, determining the location ofID node F may be based upon the fact that M2 is the closest node and theset of increasingly close nodes include M1 and M3 with M1 being closerthan M3.

In another embodiment, one or more further refinements to the firstnodes location may be performed. In one example, steps 2805-2820 may berepeated where a second of the nodes is instructed to vary the powercharacteristic for one or more signals broadcast by the second node, andthen method 2800 may further refine the location of the first node basedupon a location of the second node. In a more detailed example, steps2805-2820 may be repeated where a second of the nodes is instructed tovary the power characteristic for one or more signals broadcast by thesecond node, and then method 2800 may further the location of the firstnode based upon a location of the second node and a set of increasinglyclose nodes to the second node. With this increasingly cross-relatedinformation on what nodes are closer to other nodes and to what degree,which may be further repeated for additional nodes, embodiments mayfurther refine the location of the first node within the network.

Method 2800 may further include determining context data related to thefirst node, and refining the location of the first node based upon thecontext data. In an embodiment where the power characteristic is outputpower level, the incremental changes in the output power level of thebroadcast signal in steps 2805-2815 may be set according to the contextdata.

Method 2800 may also determine the context data to be related to theclosest node to the first node, and refine the location of the firstnode based upon the context data. In still another example, method 2800may determine the context data to be related to the incrementallyidentified nodes in the set of increasingly close nodes to the firstnode, and refining the location of the first node based upon the contextdata. For example, the closest node and the set of increasingly closenodes may have scan data that indicate they are within the samecontainer. This exemplary context data may be used to further refine thelocation of the node being located, which may help efficiently determinethat node is near the container. As such, those skilled in the willappreciate that context data for the node being located as well as nodesidentified to be close to that node may provide relevant input toadvantageously help further refine the location of the node.

Those skilled in the art will appreciate that method 2800 as disclosedand explained above in various embodiments may be implemented on aserver apparatus, such as server 100 illustrated in FIGS. 5 and 22A,running one or more parts of server control and management code 525(e.g., the location manager). Such code may be stored on anon-transitory computer-readable medium such as memory storage 515 onserver 100. Thus, when executing code 525, the server's processing unit500 may be operative to perform operations or steps from the exemplarymethods disclosed above, including method 2800 and variations of thatmethod.

An embodiment of such a server apparatus may include a server (such asserver 100) operative to communicate with a plurality of nodes in thewireless node network. As explained with respect to FIG. 5, the servergenerally includes a server processing unit, a server volatile memory, aserver memory storage, and at least one communication interface. In thisembodiment, the volatile memory, memory storage, and communicationinterface are each coupled to the processing unit. The memory storagemaintains at least a program code section and location data related to alocation of one or more of the nodes. The communication interfaceprovides a communication path operatively coupling the server with thenodes.

The server processing unit, as mentioned above, is operative whenrunning the program code section, to perform the steps and operations asdescribed above relative to method 2800 and variations of that methoddescribed above.

Proximity when Observing Signal Patterns and Strengths Over a TimePeriod

In another embodiment, an improved method for determining a node'slocation through proximity may include analyzing the signal patterns andstrengths between an advertising node and a listening node. In oneembodiment, a threshold may be set for association based on an observedmessage count and/or recorded signal strength within a specific timeperiod may improve the ability to locate a node (e.g., an ID node) tothat of another node (e.g., a master node). In some embodiments, theobserved message count may be implemented as an averaged count over arepeated time periods. Further still, other embodiments may filteroutlying observations in the observation data set to help improve thequality of data relied upon for setting a threshold for association and,as a result, determine a node's location.

In a more detailed example, an improved method for determining a node'slocation through proximity may show captured advertising message countsas a component for a node's location and determining a node's directionof travel. In this example, two exemplary master nodes (e.g., masternode M1 910 a and M2 910 b) may capture advertising messages from one IDnode (e.g., ID node A 920 a). Master node M1 may observe and capture(e.g., record information related to the observation) 60 messages fromID node A within a 2 minute period, while master node M2 only observesand captures 7 advertising messages from ID node A within that sameperiod. Based upon the difference in how often messages are observedfrom ID node A by master node M1 compared to those observed by masternode M2, the system is able to determine that ID node A would moreproximate to master node M1, and it's known location.

In a further embodiment, comparing the average time stamp of thecaptured records may allow the system can make a more accuratedetermination of location. For example, if the average captured messagefound on master node M2 is increasingly growing larger (e.g., takinglonger for messages to go from ID node A to master node M2), thisindicates ID node A is moving away from master node M2. If the averagecaptured message found on master node M2 is growing increasingly largerwhile the average captured message found on master node M1 isincreasingly growing smaller, this indicates ID node A is moving awayfrom master node M2 and toward master node M1. Thus, over a number ofobserved time periods, the change in message timing (transmission toreception) may also be relied upon to enhance or refine a node'slocation.

In yet another embodiment, the observed signal strength may be acomponent in location determination and estimating direction of traveland may allow the system can make a more accurate determination oflocation. For example, two master nodes (M1 910 a and M2 920 b) may becapturing advertising messages from a node (ID node A 920 a). M1captures 60 messages from ID node A within 2 minutes, while M2 capturesonly 7 messages. The average signal strength observed for signals fromID node A by master node M1 is higher compared to the average signalstrength observed by master node M2. Based upon this observed signalstrength information, the system would determine that ID node A to be atM1, but a predicted path may indicate ID node A is heading towards M2.As the master nodes M1 and M2 continue to capture records, the system(e.g., management code 524 operating on server 900, which is incommunication with M1 and M2) processes the continued feed of capturerecords from M1 and M2. With this observed signal strength information,the server 900 would expect that the count and average signal strengthof messages from ID node A over the time period observed (2 minutes) toincrease for observations at M2 and to decrease for observations at M1when ID node A is physically moving closer to M2 and away from M1. Thus,the change in observed powers levels and in how often messages areobserved may indicate actual node movement in an embodiment.

Basing node proximity location and node directional determinations onobserved signal patterns and characteristic strengths over a period oftime has the advantage of reducing the likelihood of unwanted andspurious signal anomalies causing an ID node's location to beincorrectly determined. And the above exemplary methods for determiningmovement characteristics of a node (e.g., moving closer to one node,moving closer to one but away from another, etc.) as part of refiningthe node location may be applied in combination with the variousembodiments for determining node location described herein.

FIG. 27 is a flow diagram illustrating an exemplary method for proximitylocating a node in a wireless node network based upon observed signalpatterns and characteristic indications over a period of time inaccordance with an embodiment of the invention. Referring now to FIG.27, method 2700 begins at step 2705 by instructing a first and a secondother nodes to detect any message broadcast from the one node over aperiod of time. The period of time may be set based upon a variety offactors, such as context data. In more detail, the period of time may bedynamically changed based upon context data as the one node moves intodifferent contextual environments.

Method 2700 has the server receiving a first indication from the firstother node at step 2710 and receiving a second indication from thesecond other node at step 2715. Finally, the method 2700 determines alocation of the one node based upon a difference in the first indicationand the second indication at step 2720.

The first indication is related to a characteristic of messagesbroadcast from the one node that are detected by the first other nodeduring the period of time. Likewise, the second indication is related tothe characteristic of messages broadcast from the one node that aredetected by the second other node during the period of time. Theseindications may include, for example, a count of messages received bythe respective other nodes, a transit time factor (e.g., an averagetransit time for a message to be detected after broadcast), and anaverage signal strength.

In one embodiment, the first indication may be a first count of messagesbroadcast from the one node that are detected by the first other nodeduring the period of time, and the second indication may be a secondcount of messages broadcast from the one node that are detected by thesecond other node during the period of time. As such, determining thelocation of the one node may be the location that is closer to the firstother node than the second other node when the first count is greaterthan the second count. Additionally, the method 2700 may further includedetermining an actual node movement direction for the one node basedupon comparing the first count and the second count over a plurality oftime periods. For example, the method 2700 may repeat observations overseveral of these time periods and track the first count and second countover time to determine which is increasing, which is decreasing, anddetermine movement of the one node based upon these measurements overtime.

In another detailed embodiment, the first indication may be a first timefactor of messages broadcast from the one node that are detected by thefirst other node during the predetermined time period, and the secondindication may be a second time factor of messages broadcast from theone node that are detected by the second other node during the period oftime. And an actual node movement direction for the one node may bebased upon comparing the first time factor and the second time factor.In a more detailed embodiment, the first time factor may be an averagetransit time for a message detected at the first other node to go fromthe one node to the first other node, and the second time factor is anaverage transit time for a message detected at the second other node togo from the one node to the second other node. As such, determining thelocation of the one node may be that the location is closer to the firstother node than the second other node when the first time factor is lessthan the second time factor.

In yet another embodiment, the first indication may be a first averagesignal strength of messages broadcast from the one node that aredetected by the first other node during the period of time, and thesecond indication may be a second average signal strength of messagesbroadcast from the one node that are detected by the second other nodeduring the period of time. As such, determining the location of the onenode may be that the location is closer to the first other node than thesecond other node when the first average signal strength is greater thanthe second average signal strength.

The method 2700 may also include, in an embodiment, observing a degreeof change in the first average signal strength and a degree of change inthe second average signal strength over repeated time periods, anddetermining an actual node movement direction for the one node basedupon comparing the degree of change in the first average signal strengthand the degree of change in the second average signal strength.

In another embodiment, the method 2700 may also refine the determinedlocation of the one node. In this embodiment, the method 2700 mayfurther comprise refining the location of the one node based upon atleast one of a first updated location received from the first other nodeand a second updated location received from the second other node. Forexample, when first other node is a mobile master node and it is thecloser of the two nodes to the one node being located, the embodimentcan take advantage of the location signaling onboard the first othernode that provides the current location of the first other node. Thatcurrent location data may be transmitted by the first other node to theserver to update the server in its calculation of the location for theone node.

In still another embodiment, the method 2700 may layer context data withthe determined location to refine the location of the node. Context datarelated to the one node may be determined by the server, and so thelocation of the one node may be refined based upon that context data. Inanother example, context data related to the closer of the first othernode and the second other node when compared to the location of the onenode. For example, the server may be aware that a particular master nodeis closer to the one node compared to a second master node, and that theparticular master node is within a container. With this additionalcontext data related to the particular master node, the server mayrefine the location of the one node based upon the context data. Otherexemplary types of relevant context data may be relied upon whenrefining the location of the one node, such as context data of aparticular shielding associated with the environment near the particularmaster node (e.g., a particular type of ULD having known RF shieldingcharacteristics, etc.)

Additionally, the method 2700 may involve looking to see if the one nodeis behaving as expected. More specifically, a further embodiment of themethod 2700 may further compare the location of the one node to apredicted path of the one node to determine if the one node is locatedoutside the predicted path. This may allow the server to use learned,historic data when creating a predicted path, and keep track of the onenode relative to being within an acceptable range associated with thispredicted path. The method may also generate a notification if the onenode is outside the predicted path. In this manner, actionable tasks canthen be taken to locate the one node—e.g., changing filter mode optionsfor nodes in that general area, etc.

Those skilled in the art will appreciate that method 2700 as disclosedand explained above in various embodiments may be implemented on aserver, such as server 100 illustrated in FIGS. 5 and 22A, running oneor more parts of server control and management code 525 (e.g., thelocation manager). Such code may be stored on a non-transitorycomputer-readable medium such as memory storage 515 on server 100. Thus,when executing code 525, the server's processing unit 500 may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 2700 and variations of that method.

Association Driven Locating with Variable RF Characteristics

As noted above, a signal strength measurement between two or more nodesmay be used to determine relative distance between nodes. If one of thenodes has a known location (such as master node M1 910 a), a relativelocation of one or more nodes within a range of the known location nodeis generally a function of how accurate the system may determine adistance between the node with known location and associated nodes. Inother words, an embodiment may identify a relative location of an itemand its related node by relying upon association-driven variablelow-power RF output signals to determine a distance the node is from aknown location.

Location Determination Through Master Node Advertise

As generally mentioned above, determining node location may relate tocontrolling an RF characteristic of a node (e.g., an RF output signallevel and/or RF receiver sensitivity level) and, more specifically, mayinvolve aspects of controlling master node advertising. FIG. 13 is adiagram illustrating an exemplary location determination using masternode advertise in accordance with an embodiment of the invention. In theillustrated embodiment shown in FIG. 13, a master node, such as masternode M1 910 a, with a known location is broadcasting an advertisingmessage at varying RF output power levels. FIG. 13 illustrates theexemplary different RF output power levels as concentric ranges1305-1315 about master node M1 910 a. Thus, master node M1 910 a maybroadcast at a maximum power P1, related to range 1305, but may controlthe RF output power level and dynamically change the RF output powerlevel to P2 and broadcast at a smaller range 1310, or to P3 andbroadcast to an even smaller range 1315.

In the illustrated embodiment, receiving ID nodes A-E 920 a-920 e are inquery (scan) mode and can each use the received signal at differentlevels to determine how far away from the transmitting M1 they arelocated. Those skilled in the art will appreciate that while theillustrated embodiment shown in FIG. 13 has the receiving nodes all asID nodes, other embodiments may have receiving nodes be either master orID nodes or a mixture.

In the exemplary embodiment of FIG. 13, the location for nodes A-E maybe determined based upon the known location of master node M1 910 a.That location, plus a range measurement when each of respectivereceiving nodes A-E last receives a signal from node M1, and factoringin a confidence factor of the range measurement, provides a locationdetermination for the nodes according to variable RF signal power.Depending on a quality of the range measurement, the individualreceiving nodes may or may not have an individually calculated location.In yet another embodiment, if third party or context data, such as scaninformation, is available, a refined location may be determined usingsuch data as an additional confidence factor. As the communication rangeof M1 is limited from P1 to P3, the accuracy of location by associationgoes up.

In the illustrated example of FIG. 13, an exemplary method ofdetermining a node's location may be described that uses master nodeadvertising. First, when the master node M1's variable power short rangecommunication interface 480 is set to P1, its maximum output, masternode M1 910 a is seen by each of ID nodes A-E 920 a-920 e. Based uponanalytics or historic measurements, the open air performance (optimalrange) of the radio in M1's variable power short range communicationinterface 480 at P1 power level may have been previously been found tobe approximately 30 feet. Thus, without the need to examine RSSI levelsfrom the individual ID nodes A-E 920 a-920 e and without the need foractive calibration phases, the system may know that ID nodes A-E arewithin 30 feet of master node M1 910 a.

Next, when the master node M1's variable power short range communicationinterface 480 is set to P2, a medium output level in this example,master node M1 is seen by nodes A and B. From previous analytics orhistoric measurements, it was determined the open air performance(optimal range) of the master node M1's variable power short rangecommunication interface 480 running at P2 power level is approximately15 feet. Thus, without the need to examine RSSI levels from theindividual nodes, we know ID nodes A 920 a and B 920 b are within 15feet of master node M1. Furthermore, we know the ID nodes no longerreceiving the broadcasted RF signal from master node M1 910 a (e.g., IDnodes C 920 c, D 920 d, and E 920 e) are somewhere within 30 feet ofmaster node M1 910 a, but probably more than 15 feet away from M1.

And when the master node M1's variable power short range communicationinterface 480 is set to P3, its minimum output level in this example, itis seen by ID node B 920 b. From previous analytics or historicmeasurements, it was determined the open air performance (optimal range)of the master node M1's variable power short range communicationinterface 480 running at P3 power level is approximately 5 feet. Thus,without the need to examine RSSI levels from the individual ID nodes, weknow the location of ID node B 920 b is within 5 feet of the knownlocation of master node M1 910 a.

The ranging steps, as discussed in the example above, may then berepeated for any of the identified nodes in order to build a moreaccurate picture of the relative location of each node. The granularityof RF characteristic settings (e.g., the RF output signal power levelsetting) will provide more granularity of location differentiation whenperforming the ranging steps. In one embodiment, the ranging steps maybe performed over a set of gross RF characteristics settings (e.g., fewsettings over a wide range), and similar steps may then be performedover more select ranges for the RF characteristics settings.

FIG. 29 is a flow diagram illustrating an exemplary method for locationdetermination using one or more associations of nodes in a wireless nodenetwork in accordance with an embodiment of the invention. Referring nowto FIG. 29, method 2900 begins at step 2905 where a first of the nodesbroadcasts one or more first messages at a first anticipated orpredicted range distance. In one embodiment, the first anticipated rangedistance is an optimal range for the first node. For example, the firstnode's radio in its communication interface may have a maximum settingto allow the node to broadcast at maximized range assuming a clearenvironment. Such a setting provides a known anticipated range distance.In the example of FIG. 13, master node M1 910 a may be broadcasting at amaximum power level P1 that reaches a first range distance from node M1.However, if node M1 is known to be within an adverse RF shieldingenvironment, the first anticipated range distance may be a distanceadjusted to account for the contextual environment of such shielding(e.g., a type of context data). Anticipated range distances may beadjusted depending upon one or more types of relevant context (e.g., oneor more types of context data related to how an RF output signal fromthe node may be impeded).

At step 2910, method 2900 identifies which of the nodes associated withthe first node received at least one of the first messages. In oneembodiment, the first node may be able to access and review associationdata in its onboard memory storage as part of identifying which are thenodes associated with it. In one example, the associations with thefirst node may be passive associations (e.g., not actively paired andsecurely connected) or active associations (e.g., actively paired andable to securely connect and share data), or a combination of both typesof associations.

Next, at step 2915, the first node broadcasts one or more secondmessages at a second anticipated range distance, which is incrementallysmaller than the first anticipated range distance. In the example ofFIG. 13, master node M1 910 a may be the first node and now isbroadcasting at a medium power level P2 that reaches a secondanticipated range distance from node M1. By incrementally changing theRF power level in this manner, master node M1 910 a now no longer canreach nodes C-E as shown in FIG. 13.

At step 2920, method 2900 concludes by determining a location of one ormore of the identified associated nodes that did not receive any of thesecond messages but received at least one of the first messages, wherethe location is between the first and second anticipated range distancesfrom the first node. Again, in the example of FIG. 13, master node M1910 a may determine the location of nodes C-E (given they did notreceive the message sent out the second anticipated range distance at RFpower level P2) to between the first anticipated range distance (whenmaster node M1 was broadcasting at power level P1) and the secondanticipated range distance (when master node M1 was broadcasting atpower level P2) from the known location of master node M1.

In one embodiment, the method 2900 may also have the first nodebroadcasting one or more third messages at a third anticipated rangedistance (incrementally smaller range than the second anticipated rangedistance), and determining a location of one or more of the identifiedassociated nodes that did not receive any of the third messages butreceived at least one of the second messages, where the location isapproximately near the second anticipated range distance from the firstnode. Again, in the example of FIG. 13, by incrementally changing thepower level down to P1 and broadcasting a third message at ananticipated range distance for that P1 level, the master node M1 candetermine the location of node A (as node A received the second messagebut did not receive the third message) to be approximately near theanticipated range distance for P2 from the location of master node M1.

Additional embodiments of method 2900 may also refine such determinedlocations by updating the location of the first node. In one embodiment,the first node may be a mobile node. As such, refining may involvedetermining a current mobile location of the first node, and refiningthe location of the one or more of the identified associated nodes thatdid not receive any of the second messages but received at least one ofthe first messages based upon the current mobile location of the firstnode. Thus, as the first node moves and updates its own location (e.g.,via GPS signals received by location circuitry 475 on a master node),the first node is able to leverage its own updated location andadvantageously refine the location of nodes associated with it.

And, in some embodiments, the refined location of associated nodes maybe transmitted to a server. This provides an update to the server, andaids in tracking and managing the location of nodes in the network.Again, referring back to the example of FIG. 13, master node M1 910 amay take advantage of such a method for locating associated nodes, suchas the locations of ID nodes A-E 920 a-920 e, and update server 100 withthis new location data related to the current location of node M1 andany of the nodes associated with node M1.

Those skilled in the art will appreciate that method 2900 as disclosedand explained above in various embodiments may be implemented on a node(e.g., master node 110 a in FIG. 4, master node M1 910 a in FIG. 13, ormaster node M1 2210 a in FIG. 22A) running one or more parts of mastercontrol and management code 425 (e.g., the location aware/capturemodule). Such code may be stored on a non-transitory computer-readablemedium, such as memory storage 415 on master node 110 a. Thus, whenexecuting code 425, the master node's processing unit 400 may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 2900 and variations of that method.

In another embodiment, a node apparatus is described in a wireless nodenetwork that uses location determination by association as describedwith reference to the steps related to method 2900. As mentioned above,such as node apparatus may be implemented with a master node having anode processing unit, a node volatile memory, a node memory storage, anda first and second communication interface. Each of the memories andcommunication interfaces are coupled to the node processing unit.Further, the node memory storage maintains at least a program codesection, association data, and location data and, at times, shippinginformation. The first communication interface provides a firstcommunication path operatively coupling the node with a plurality ofother nodes in the network, while the second communication interfaceprovides a second communication path operatively and separately couplingthe node with a server in the network.

In this embodiment, the node processing unit is operative to transmitone or more first messages via the first communication interface at afirst anticipated range distance, and identify which of the others nodesthat are associated with the first node received at least one of thefirst messages. In one embodiment, the node processing unit may beoperative to access the association data in the node memory storage whenidentifying which of the nodes associated (e.g., passive, active, orboth types of associations) with the first node received at least one ofthe first messages.

The first anticipated range distance may be an optimal transmissionrange for the first communication interface and, in a more detailedexample, may be adjusted based upon context data (e.g., RF shieldinginherent from the surrounding environment of the node). In yet anotherembodiment, the first anticipated range distance and the secondanticipated range distance may be adjusted based upon one or more typesof context data related to how an RF output signal transmit from thefirst communication interface may be impeded by an environment of thenode.

The node processing unit is also operative to transmit one or moresecond messages via the first communication interface at a secondanticipate range distance (incrementally smaller than the firstanticipated range distance) and determine a location of one or more ofthe identified associated nodes that did not receive any of the secondmessages but received at least one of the first messages. That locationis between the first anticipate range distance from a known location ofthe node and the second anticipated range distance from the knownlocation of the node. In a further example, the node processing unit maybe operative to store the determined location in the node memory storageas part of the location data.

The node processing unit may also be operative to transmit one or morethird messages via the first communication interface at a thirdanticipated range distance (incrementally smaller range than the secondanticipated range distance) and determine a location of one or more ofthe identified associated nodes that did not receive any of the thirdmessages but received at least one of the second messages, where thelocation is between the second anticipated range distance from the knownlocation of the node and the third anticipated range distance from theknown location of the node.

In another embodiment, the node may be mobile and the node processingunit may be further operative to refine the location of the one or moreof the identified associated nodes that did not receive the secondmessage but received the first message by updating a location of thefirst node. In more detail, the node processing unit may be operative todetermine a current mobile location of the first node (e.g., check withlocation circuitry onboard the node for valid GPS signals and a locationlock based on such signals), and refine the location of the one or moreof the identified associated nodes that did not receive any of thesecond messages but received at least one of the first messages basedupon the current mobile location of the first node. The node processingunit may also be operative to transmit the refined location to theserver over the second communication interface.

Location Determination through ID Node Advertise

While FIG. 13 provides an example of location determination throughmaster node advertising, FIG. 14 focuses on location determinationthrough ID node advertising. In particular, FIG. 14 is a diagramillustrating an exemplary location determination using ID node advertisein accordance with an embodiment of the invention. In the illustratedembodiment shown in FIG. 14, exemplary ID node F 920 f is in anadvertising mode but is without a known location. As with FIG. 13, FIG.14 illustrates the exemplary different RF output power levels from IDnode F 920 f as concentric ranges 1405-1415 about ID node F 920 f. Thus,ID node F 920 f may broadcast at a maximum power P1, related to range1405, but may control the RF output power level and dynamically changethe RF output power level to P2 and broadcast at a smaller range 1410,or to P3 and broadcast to an even smaller range 1415. Master nodes M1-M3910 a-910 c are disposed in various known locations relatively near IDnode F 920 f, which has an unknown location. As such, ID node F 920 fmay take advantage of the ability to adjust an RF characteristic, suchas RF output signal power level, of its own short-range communicationinterface as part of how the system may determine location of ID node Fthrough ID node advertising.

In the illustrated embodiment, an RF output signal power level of IDnode F 920 f may be varied or dynamically adjusted via programmablesettings (such as profile settings or parameters) related to operationsof variable power short range communication interface 375. Additionally,while an actual communication range may vary with the surroundingenvironment, a maximum anticipated communication range of the ID node'stransmitter at each power level is known assuming an optimal operatingenvironment or no substantial RF shielding or interference. Thus, aparticular power level setting for a broadcasting node is inherentlyassociated with a corresponding anticipated range distance.

In an exemplary method of determining a nodes location using ID nodeadvertising, the RF output signal power level may be varied acrossmultiple power levels to improve location through master nodeassociation. In more detail, when the ID node F's variable power shortrange communication interface 375 is set to P1, its maximum output, IDnode F 920 f is seen by each of master nodes M1-3 910 a-910 c. Theanticipated open air performance or range distance (optimal range, orrange based upon analytics or historic measurements) of the radio in IDnode F's variable power short range communication interface 375 at P1power level may have been previously been found to be approximately 30feet. Thus, without any examination of RSSI levels from the individualmaster nodes, the system knows ID Node F is within 30 feet of masternodes M1-M3.

Next, when the ID node F's variable power short range communicationinterface 375 is set to P2, a medium output level in this example, IDnode F 920 f is seen by master nodes M1 910 a and M2 910 b. Theanticipated open air performance or range distance (optimal range, orrange based upon analytics or historic measurements) of the radio in IDnode F's variable power short range communication interface 375 atrunning at P2 power level is approximately 15 feet. Thus, without anyexamination of RSSI levels from the individual nodes, we know masternodes M1 910 a and M2 910 b are within 15 feet of ID node F 920 f inthis example. Furthermore, we know the master node no longer receivingthe broadcasted RF signal from ID node F 920 f (e.g., master node M3 910c) is somewhere within 30 feet of ID node F 920 f, but probably morethan 15 feet away from node F in this example.

And when ID node F's variable power short range communication interface375 is set to P3, its minimum output level in this example, ID node F920 f is seen by only master node M2 910 b. The anticipated open airperformance or range distance (optimal range, or range based uponanalytics or historic measurements) of the radio in ID node F's variablepower short range communication interface 375 at P3 power level isapproximately 5 feet. Thus, without any examination of RSSI levels fromthe master nodes, we know the location of ID node F 920 f is within 5feet of the known location of master node M2 910 b in this example.

The ranging steps with respect to the changed RF characteristics of anadvertising ID node, as discussed in the example above, may then berepeated for any of the identified nodes in order to building a morecomplete picture of the relative location of each node.

Furthermore, the timing between such ranging steps may vary dynamicallydepending upon whether the node is moving. Those skilled in the art willappreciate that when moving, a quicker flow through such ranging stepswill help to provide better accuracy given the movement of nodes. Thus,the time interval between instructing a node to broadcast one or moremessages at a particular power level and then instructing that node tobroadcast one or more messages at a different power level may be desiredto be shorter when the node is moving, which can be determined basedupon context data. For example, the context data may indicate the nodeis within a node package an on a moving conveyor system. As such, thenode is moving relative to fixed master nodes that may be positionedalong the conveyor system. Thus, server may have the first node performthe ranging steps where power is varied in relative quick successioncompared to a situation where the context data indicates the node is notmoving or is substantially stationary.

FIG. 30 is a flow diagram illustrating another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention.Referring to FIG. 30 and how it explains a particular way to locate anode using associations and master node one or more master nodeadvertising techniques, method 3000 begins at step 3005 by instructing afirst of the nodes to broadcast one or more first messages at a firstpower level, the first power level being related to a first anticipatedrange distance. In one example, the first anticipated range distance maybe an optimal range for the first of the nodes (e.g., a transmissionrange that assumes there are no obstructions and a clear signal pathbetween nodes). In another example, the first anticipated range distancemay be an optimal range for the first node adjusted based upon contextdata (e.g., data related to the surrounding RF environment of the firstnode).

At step 3010, the method 3000 identifies which of the nodes associatedwith the first node have known locations at step 3010. For example, thistype of identification may be accomplished by reviewing association datathat indicates which of the nodes are associated with the first node(e.g., via passive association, via active association, or via acombination of both), determining which of the nodes are associated withthe first node based upon the reviewed association data, and identifyingwhich of those associated nodes have known locations.

The method 3000 continues at step 3015 by determining which of theidentified associated nodes received at least one of the first messages.Next, the method 3000 instructs the first node at step 3020 to broadcastone or more second messages at a second power level, where the secondpower level is related to a second anticipated range distance and thesecond power level incrementally smaller than the first power level. Ina further example, the first anticipated range distance and the secondanticipated range distance may be adjusted based upon one or more typesof context data related to how an RF output signal from the first nodemay be impeded.

At step 3025, method 3000 determines which of the identified associatednodes received at least one of the second messages. Method 3000concludes at step 3030 where the method determines a location of thefirst node to be at or between the first anticipated range distance andthe second anticipated range distance from each of the identifiedassociated nodes that did not receive at least one of the secondmessages but received at least one of the first messages.

As mentioned above, determining the node's location may be improved whenaccounting for movement. As such, an embodiment of method 3000 mayinstruct the first node to broadcast the one or more second messageswithin a time interval after instructing the first node to broadcast theone or more first messages. The time interval may be predetermined insome implementations, but also may be a dynamically set parameter inother implementations based upon context data related to the first node.In more detail, the time interval may be reduced from a prior value whenthe context data related to the first node indicates the first node ismoving, but may be increased from a prior value when the context datarelated to the first node indicates the first node is substantiallystationary.

In another embodiment, method 3000 may further include instructing thefirst node to broadcast one or more third messages at a third powerlevel. Such a third power level is related to a third anticipated rangedistance and incrementally smaller range than the second anticipatedrange distance. Thereafter, the method may determining the location ofthe first node to be at or between the second anticipated range distanceand the third anticipated range distance from each of the identifiedassociated nodes that did not receive any of the third messages butreceived at least one of the second messages.

In another embodiment, method 3000 may comprise refining the location ofthe first node with an updated location of one or more of the identifiedassociated nodes that did not receive at least one of the secondmessages but received at least one of the first messages. For example,if the first node is associated with a mobile master node, the locationof the first node may be refined with an updated location of the mobilemaster node (which may be closer to the first node than previouslydetermined).

In a further embodiment, the first node in the operation of method 3000may not be self-aware of its own location. In another embodiment, thefirst node in the operation of method 3000 may have been previouslyself-aware of the location of the first node but may no longer beself-aware of the location of the first node prior to broadcasting theone or more first messages. In more detail, the first node may no longerbe self-aware of the location of the first node prior to broadcastingthe first message because of a change in the environment surrounding thefirst node. Such a change in the environment may be, for example, whenthe first node has moved inside a structure (e.g., building, vehicle,aircraft, container, etc.) that blocks location signals from beingreceived by the first node.

Those skilled in the art will appreciate that method 3000 as disclosedand explained above in various embodiments may be implemented on a node(e.g., master node 110 a in FIG. 4) running one or more parts of mastercontrol and management code 425 (e.g., the location aware/capturemodule) to control operations of an ID node (such as ID node F in FIG.14) as part of location determination via ID node advertising. Such codemay be stored on a non-transitory computer-readable medium, such asmemory storage 415 on master node 110 a. Thus, when executing code 425,the master node's processing unit 400 may be operative to performoperations or steps from the exemplary methods disclosed above,including method 3000 and variations of that method.

From an apparatus perspective, an exemplary node apparatus in a wirelessnode network that uses location determination by association maycomprises a node processing unit, node memory coupled to and used by thenode processing unit (e.g., a node volatile memory and a node memorystorage). The node memory storage maintains at least a program codesection, association data, and location data. The node apparatus furtherincludes a first communication interface that provides a firstcommunication path coupled to the node processing unit and operativelycoupling the node with a plurality of other nodes in the network. Forexample, the master node 110 illustrated in FIG. 4 includes such typesof operational structure.

The node processing unit (e.g., processing unit 400 of master node 110a), when executing at least the program code section resident in thenode volatile memory, is operative to perform specific functions orsteps. In particular, the node processing unit is operative tocommunicate an instruction to a first of the other nodes (e.g., an IDnode or master node temporarily operating as an ID node) via the firstcommunication interface to cause the first other node to broadcast oneor more first messages at a first power level, where the first powerlevel is related to a first anticipated range distance.

The first anticipated range distance may be an optimal range for thefirst of the nodes and, in more detail, an optimal range for the firstof the nodes adjusted based upon context data. In even more detail, thefirst anticipated range distance and the second anticipated rangedistance may be adjusted based upon one or more types of context datarelated to how an RF output signal broadcast from the first node may beimpeded.

The node processing unit is also operative to identify which of thenodes associated with the first node have known locations. To do this,the node processing unit may access and review association data storedon the node memory storage (e.g., data indicating what nodes arepassively or actively associated with the first other node), maydetermine which of the remaining other nodes are associated with thefirst other node based upon the reviewed association data, and mayidentify which of the remaining other nodes determined to be associatedwith the first other node have known locations.

The node processing unit is also operative to determine which of theidentified associated nodes received at least one of the first messages,and to communicate another instruction via the first communicationinterface to the first node to cause the first node to broadcast one ormore second messages at a second power level, where the second powerlevel being is to a second anticipated range distance and incrementallysmaller than the first power level.

Finally, the node processing unit is operative to determine which of theidentified associated nodes received at least one of the secondmessages, and then determine a location of the first node to be at orbetween the first anticipated range distance and the second anticipatedrange distance from each of the identified associated nodes that did notreceive at least one of the second messages but received at least one ofthe first messages.

In a further embodiment, the node processing unit may be operative tocommunicate a third instruction via the first communication interface tothe first node to cause the first node to broadcast one or more thirdmessages at a third power level. The third power level is related to athird anticipated range distance and incrementally smaller range thanthe second anticipated range distance. Additionally, the node processingunit may then be operative to determine the location of the first nodeto be at or between the second anticipated range distance and the thirdanticipated range distance from each of the identified associated nodesthat did not receive any of the third messages but received at least oneof the second messages.

In still another embodiment, the node processing unit is able to accountfor movement of the first node with a time interval between instructionssent to the first node. In particular, the node processing unit may befurther operative to communicate another instruction via the firstcommunication interface to the first node to broadcast the secondmessages within a time interval after instructing the first node tobroadcast the first messages. In a more detailed example, the timeinterval may be dynamically set based upon context data related to thefirst node. In even more detail, the time interval may beprogrammatically reduced from a prior value when the context datarelated to the first node indicates the first node is moving (e.g., thefirst node is on a moving conveyor system) and/or the time value of theinterval may be increased from a prior value when the context datarelated to the first node indicates the first node is substantiallystationary (e.g., the node is within a node package recently placed in astorage area).

The node processing unit, in a further embodiment, may be operative torefine the location of the first other node with an updated location ofone or more of the identified associated nodes that did not receive atleast one of the second messages but received at least one of the firstmessages, and cause a second communication interface (e.g., medium/longrange communication interface 485 coupled to processing unit 400) totransmit the refined location to the server.

From a server perspective, FIG. 31 is a flow diagram (similar to FIG.30) illustrating yet another exemplary method for location determinationusing one or more associations of nodes in a wireless node network inaccordance with an embodiment of the invention. Those skilled in the artwill appreciate that while a server may operate to implement the stepsas laid out in method 3000 and discussed above, FIG. 31 provides moredetails as to how a server processing unit (such as processing unit 500running server code 525) may implement such a method at that level ofthe network via method 3100. In this more detailed embodiment, theserver is communicating directly with a master node (e.g., a first node)to direct and control how the master node interacts with and causesoperations to be undertaken on the ID node (e.g., a second node). Thus,step 3105 is similar to step 3005 but more precisely calls forcommunicating with a first node via a communication interface to cause asecond node in the network to broadcast one or more first messages at afirst power level at the request of the first node, where the firstpower level is related to and corresponds with a first anticipated rangedistance. Likewise, step 3120 is similar to step 3020 but more preciselycalls for communicating with the first node via the communicationinterface to cause the second node to broadcast one or more secondmessages at a second power level at the request of the first node, thesecond power level being related to a second anticipated range distanceand incrementally smaller than the first power level. The other steps ofmethod 3100 are similar to those illustrated and explained aboverelative to method 3000, and that the similar principles will apply tomethod 3100.

Those skilled in the art will appreciate that method 3100 as disclosedand explained above in various embodiments may be implemented on aserver (e.g., server 100 in FIG. 5) running one or more parts of servercontrol and management code 525 to direct a master node to controloperations of an ID node (such as ID node F in FIG. 14) as part oflocation determination via ID node advertising. Such code may be storedon a non-transitory computer-readable medium, such as memory storage 515on server 100. Thus, when executing code 525, the server's processingunit 500 may be operative to perform operations or steps from theexemplary methods disclosed above, including method 3100 and variationsof that method.

And similar to the node apparatus described above, one embodimentincludes an exemplary server apparatus in a wireless node network thatuses location determination by association. The exemplary serverapparatus generally comprises a server processing unit, server memorycoupled to and used by the server processing unit (e.g., a servervolatile memory and a server memory storage). The server memory storagemaintains at least a program code section, association data, andlocation data. The server apparatus further includes a communicationinterface coupled to the server processing unit and that provides accessto a communication path operatively coupling the server with at least afirst node in the network.

The exemplary server processing unit, when executing at least theprogram code section resident in the server volatile memory, isoperative to perform specific functions or steps. In particular, theserver processing unit is operative to communicate with the first nodevia the communication interface to cause a second node in the network tobroadcast one or more first messages at a first power level at therequest of the first node, where the first power level is related to afirst anticipated range distance; identify which of the remaining nodesin the network associated with the second node have known locations;determine which of the identified associated nodes received at least oneof the first messages; communicate with the first node via thecommunication interface to cause the second node to broadcast one ormore second messages at a second power level at the request of the firstnode, where the second power level is related to a second anticipatedrange distance and incrementally smaller than the first power level;determine which of the identified associated nodes received at least oneof the second messages; and determine a location of the second node tobe at or between the first anticipated range distance and the secondanticipated range distance from each of the identified associated nodesthat did not receive any of the second messages but received at leastone of the first messages. And in a further embodiment, the serverapparatus' processing unit may be further operative to store thedetermined location in the server memory storage as part of the locationdata.

In another embodiment, the server apparatus' processing unit may beoperative to communicate with the first node via the communicationinterface to cause the second node to broadcast the one or more secondmessages within a time interval after communicating with the first nodeto cause the second node to broadcast the one or more first messages. Aspreviously mentioned, this type of time interval may dynamically setbased upon context data related to the second node. Context data mayalso be used as set forth above with respect to the node apparatus butapplied here to the second node—such was where the first anticipatedrange distance is the optimal range for the second node adjusted basedupon context data.

Master Node Location Determination Through Advertise

In another embodiment, a master node may no longer know its location.For example, such a situation may occur when a master node determinesit's current location via GPS location circuitry 475, but the masternode finds itself without access to an adequate number of GPS signals(e.g., it cannot determine a location due to the lack of a sufficientnumber of GPS signals from diverse GPS satellites). Such a situation mayhappen when the master node moves indoors is proximate to a structurethat interferes with the location signals.

In an exemplary embodiment where a master node attempts to determine itsown location via advertising techniques, the master node may detect aloss of location confidence (e.g., upon a loss of detected GPS signals;upon detecting a separate signal to processing unit 400 indicating themaster node's location is unknown; when processing unit 400 sensesmovement (e.g., via accelerometers (not shown) or the like) but cannotconfirm that the location circuitry 475 is providing updated locationinformation for the node, etc.). In other words, the master node becomesaware that it no longer has a known location.

Next, the master node responds by beginning to broadcast one or moreadvertising messages in a similar way as ID node F 920 f is described asdoing with respect to FIG. 14. This is done so that the master nodehaving an unknown location can advantageously leverage off the knownlocations of nearby other nodes. As such, an embodiment may allow a typeof leveraged chaining effect whereby known locations of particular typesof nodes may be used to extend location information to other nodes thatdo not know their locations (e.g., ID nodes) or nodes that have detecteda loss of location confidence (e.g., master nodes). Thus, such anembodiment may be used to determine an indoor location of a master node(including equipment equipped with master node functionality) in caseswhere signals for the conventional onboard location circuitry 475 arenot available.

Referring back to the exemplary method 3000 and FIG. 30, method 3000 maybe such that the first node is not self-aware of the location of thefirst node. This may happen when the first node (e.g., an ID node) isactually a master node that was previously self-aware of its ownlocation (e.g., via received GPS signals) but is no longer self-aware ofits location (e.g., when the GPS signals can no longer be received),which has the master node changing operation to operate as an ID nodeprior to broadcasting the first message. In other words, the master nodemay no longer be self-aware of its location and begin operating as an IDnode for purposes of location determination prior to broadcasting thefirst message because of a change in the environment surrounding themaster node, such as when the master node has moved inside a structurethat blocks location signals from being received by the master node.Thus, an embodiment may advantageously allow a node to adaptively alteroperations when moving from a clear outdoor environment to an indoorenvironment. And a server may interact with such a master node whilethat master node is operating, for location purposes, as an ID node,temporarily.

Location with Improved RSSI Measurements

In another embodiment, a signal strength measurement between two or morenodes may be used to determine the proximity of the nodes by using oneor more improvements to conventional RSSI measurements. In conventionalRSSI measurements, such as with Bluetooth 4.0, those skilled in the artwill appreciate that adaptive frequency hopping as part of spreadspectrum techniques may cause undesirably cause the signal strength tofluctuate. In other words, the advantage of using frequency hopping andspread spectrum for security and avoidance of interference may have anegative impact on using such signals for stable proximity-basedlocation determinations. Thus, it may be desired to emphasize stabilityof a signal and limits to fluctuation for purposes of locationdetermination.

In one embodiment, a type of improvement for RSSI measurements mayinclude reducing the number of channels and/or a corresponding frequencyrange in use during advertising from nodes. For example, a node may haveprocessing unit 300/400 adaptively control variable power short rangecommunication interface 375/480 to reduce the number of channels and/orthe frequency range used during node advertising. Such a dynamic changemay be implemented, in some embodiments, by altering the content of aparticular type of profile data 330/430, such as an RF profile data thateffectively defines RF characteristics of a node (e.g., frequency, powerlevel, duty cycle, channel numbers, channel spacing, alternativefluctuation modes, etc.). In one further embodiment, a first fluctuationmode may be defined that provides a default or more standardcommunication protocol, such as the conventional frequency hopping,spread spectrum, and channel allocations for Bluetooth® communications.Other alternative modes (one or more) may be defined that alter one ormore RF characteristics to provide increasingly more stable and lessfluctuations of the RF output signal from a node. Thus, a node may bedynamically placed into one or more modes regarding such RFcharacteristics that increasingly emphasize stability of the node's RFoutput signal and limits fluctuation for purposes of enhanced locationdetermination using RSSI measurements.

In another embodiment, a type of improvement for RSSI measurements mayinclude ensuring visibility to and advantageously managing automaticgain control (AGC) circuitry (not shown) that may cause the RF outputsignal to vary for a node. For example, a node may include a type of AGCcircuitry as part of variable power short range communication interface375/480. This type of AGC circuitry may allow node processing unit300/400 or other logic circuitry that is part of variable power shortrange communication interface 375/480 to limit fluctuations undercertain conditions (e.g., when attempting to use RSSI locationdetermination techniques). In this example, different AGC circuitrysettings may be defined in exemplary RF profile data that effectivelydefines RF characteristics of a node (e.g., frequency, power level, dutycycle, channel numbers, channel spacing, alternative fluctuation modes,etc.). This is yet another example of how a node may be dynamicallyplaced into one or more modes regarding such RF characteristics(including AGC circuitry settings) that increasingly emphasize stabilityof the node's RF output signal and limits fluctuation for purposes ofenhanced location determination using RSSI measurements.

Location with Adjustments for Environmental Factors in RF Signal Quality

In general, those skilled in the art will appreciate that environmentalfactors may cause a communication signal, such as an RF signal, tofluctuate or be transmitted and received in a manner that undesirablyvaries depending upon a signal path environment. Passive physicalinterference factors (e.g., forms of electronic signal shielding) may besubstantially close and cause drops in signal strength across the outputranges of the nodes. Additionally, active radio interference factors mayvary across the RF output ranges of the nodes depending upon otheractive devices in the reception vicinity. Thus, the proximateenvironment of a node may have a multitude of adverse factors thatimpact communications and, as a result, the ability to locate the node.

In one embodiment, making location determinations may be enhanced by adata analytics type of approach that may adjust and account fordifferent RF environmental factors for a similar type of node in asimilar type of situation. For example, the quality of the RF outputsignal of a particular type of node and the corresponding physical rangeof that signal to a receiver of known sensitivity may be determined fora given environment. In this example, the system defines a maximum rangeof that signal based on a predetermined condition, such as open-airconnectivity. This may assume an environment with no signal degradationdue to interference or physical shielding. However, both interferenceand physical shielding may diminish the range of the RF output signal ofa node. In a dynamically adaptive and learning manner, the system maycollect information on how a particular type of node may operate in aparticular environment under certain settings (e.g., reported signalstrengths and corresponding settings for RF output signal power levels).This analysis of a similar environment may be repeated. In other words,through such data analytics of an anticipated environment to be faced bya similar node, signal loss information can be generated and applied asa type of context data (i.e., RF data) for a node in a similarenvironment to refine location determination. Thus, an exemplaryembodiment may refine location determinations with adaptive signal losscharacteristics based on a contextual appreciation of an anticipatedenvironment (e.g., physical shielding such as packaging, packagecontents, proximate package, proximate package contents, and physicalinfrastructure causing signal variance) without requiring a calibrationphase.

And advantageously combining those data points with 3^(rd) party datadescribing the physical environment, in which the node was located in atthat time, may refine location even further. Such information may beused as RF data (a type of context data) in future efforts to manage andlocate a similar type of node anticipated to be in a similarenvironment.

In more detail, in an embodiment that refines a location determinationbased upon context and data analytics to adjust for known RFimpediments, the maximum physical range of a node's RF output signalrelative to a receiver of known RF sensitivity is determined. In oneexample, this first range value may be referred to as a theoretical ornominal open-air range of a similar type transmitter-receiver node pairin a similar environment but with substantially no physical shielding orsignal interference negatively impacting the signal range. A secondrange value, which may be considered an actual RF range value, may bethe observed range of the signal in a similar environment but wherethere are contextual factors reducing the communication range, includingphysical shielding due to factors like packaging, package contents,proximate package, proximate package contents, physical infrastructure,interference from other radio sources, or shipper specific informationsuch as vehicle or facility layout information. Through access to priordata analysis of the differing range values and with knowledge of theoperational environment of the transmitting node was in (e.g., a similarenvironment to the proximate environment of the node), a refinedlocation may be determined using an approximation of an actual RF outputrange that intelligently adjusts what may be anticipated to be the RFenvironment of the node. In other words, by knowing the appropriatecontextual environment related to a node (such as signal degradationinformation on how a similar node operates in a similar environment), animproved location determination may be made to make intelligent yetefficient adjustments (such as communication distance adjustments) thatprovide a refined location of the node.

In one example, such as the example shown in FIG. 2, master node 110 bis outside of a container (such as a Uniform Load Device (ULD) container210 known to be used for transporting groups of items on aircraft) thathas an ID node inside the container. A first or theoretical range valuebetween master node 110 b and ID node 120 b may be determined to be 10feet at a specific RF output power level when the package (and relatedID node) may be known to be less than 10 feet away from the scanningnode (e.g., master node 110 b). A second range value at similardistances with similar types of nodes, but with incident RF signal lossas a result of communicating through the wall of the container 210, maybe between 4 and 5 feet. If context data, such as 3^(rd) partyinformation or scan data, indicates the transmitting node is within theULD container 210, the system would expect the transmission range to belimited according to the data analytics associated with this known RFimpediment (e.g., characteristics for transmitting through ULD container210), thus reducing the possible scanning nodes that may see thebroadcasting node within the ULD container, or require the transmittingnode to increase its RF output power to be heard.

FIG. 32 is a flow diagram illustrating an exemplary method for locationdetermination of a first node in a wireless node network based oncontext data in accordance with an embodiment of the invention.Referring now to FIG. 32, method 3200 begins at step 3205 with a networkdevice (such as a master node or server) accessing a first type of thecontext data related to a proximate environment of the first node.

The first type of context data comprises signal degradation informationon how a second node would operate in a similar environment to theproximate environment of the first node when the second node is asimilar type as the first node. Thus, rather than calibrating with anactual measurement relative to the current proximate environment of thefirst node, the signal degradation information provides compensationinformation on what may be generally anticipated in a more generalproximate environment based on how a similar type of node may operate ina similar environment. As the similar environment of the similar node isgenerally an approximation for what is anticipated to be the proximateenvironment of the first node, this advantageously avoids the need foran actual calibration of the proximate environment. In one embodiment,the signal degradation information may be based upon a difference in howthe second node communicates when exposed to an adverse communicationenvironment (such as a similar environment to the proximate environmentof the first node) compared to how the second node would communicateswhen exposed to a nominal communication environment (such as anenvironment that is unencumbered by shielding and interference factors).Those skilled in the art will appreciate that a nominal communicationenvironment need not be perfectly clear of all influences that shield orinterfere with communications.

The types and aspects of signal degradation information may varydepending on a wide variety of factors. In one embodiment, the signaldegradation information may be related to at least one of shielding andinterference. Thus, signal degradation information may include bothpassive and active factors that impact the communication environment.

In another embodiment, the signal degradation environment may be basedupon a degraded operation of the second node when the similarenvironment is an adverse communication environment. In more detail, thesignal degradation information may be based upon a difference in how thesecond node communicates when exposed to the adverse communicationenvironment compared to how the second node communicates when exposed toa substantially normal communication environment, such as an open airenvironment.

In still another embodiment, signal degradation information may relateto at least shipment data for one or more items being shipped (e.g.,currently shipped or shipped in the past) and located in the proximateenvironment of the first node. For instance, a package near the firstnode may include metallic materials that may impede or block RF signalsand the signal degradation information may relate to such informationabout close packages being shipped near the first node. In anotherexample, the signal degradation information may relate to at leastlayout data for one or more physical structures in the proximateenvironment of the first node. In more detail, the layout data may befor one or more physical structures (e.g., walls, machinery, enclosures,and conveyances) in the proximate environment of the node near apredicted path for the first node. In yet another example, the signaldegradation information relates to at least historic data on one or moreanalyzed prior operations of the second node.

At step 3210, the network device, such as a master node or server, mayadjust an anticipated communication distance related to the first nodebased upon on the first type of the context data. In one example, theanticipated communication distance may be a theoretical broadcastdistance based upon parameters of the device's radio. Such ananticipated communication distance is known as it is an estimate of theradio's range. In one example, the adjusted communication distancecomprises an anticipated reduced range distance for a transmission fromthe first node. In another example, the adjusted communication distancecomprises an anticipated reduced receiver sensitivity distance for thefirst node.

In yet another example, adjusting the communication distance may beaccomplished by adaptively adjusting, by the network device, thecommunication distance based upon the signal degradation information anda second type of the context data. In other words, the communicationdistance may be adjusted based upon signal degradation informationconsidered along with other types of context data, such as how the firstnode is being moved (such as an anticipated movement of the first nodealong a predicted transit path for the first node) or a density of othernodes near the first node.

At step 3215, the network device determines the location of the firstnode based upon the adjusted communication distance. In a furtherembodiment, the method may also update the adjusted communicationdistance by the network device based upon movement of the first node,and may refine the location of the first node with an updated adjustedcommunication distance. This may happen with the first node is a mobilemaster node capable of self-determining its own location.

Those skilled in the art will appreciate that method 3200 as disclosedand explained above in various embodiments may be implemented on anetwork device (e.g., exemplary master node 110 a in FIG. 4 or server100 in FIG. 5) running one or more parts of their respective control andmanagement code to perform steps of method 3200 as described above. Suchcode may be stored on a non-transitory computer-readable medium, such asmemory storage 415 on master node 110 a or memory storage 515 on server100. Thus, when executing such code, the respective network device'sprocessing unit may be operative to perform operations or steps from theexemplary methods disclosed above, including method 3200 and variationsof that method.

In more detail, an exemplary network device apparatus for determining alocation of a first node in a wireless node network based on contextdata, the exemplary network device may include a processing unit, avolatile memory coupled to the processing unit, and a memory storagecoupled to the processing unit. The exemplary network device furtherincludes a communication interface coupled to the processing unit andthat provides a communication path operatively coupling the networkdevice with the first node in the network.

The memory storage for the device maintains at least a program codesection and context data having at least signal degradation information.Such signal degradation information, as a type of context data, isinformation on how a second node would operate in a similar environmentto a proximate environment of the first node when the second node is asimilar type as the first node. Examples of signal degradationinformation may include those discussed above relative to step 3205 ofmethod 3200.

When executing at least the program code section when resident in thevolatile memory, the processing unit of the network device is operativeto perform the steps noted and described above with respect to method3200. In more detail, the processing unit is operative to at leastconnect with the memory storage to access the signal degradationinformation, adjust a communication distance (if needed) related to thefirst node based upon on the signal degradation information, determinethe location of the first node based upon the adjusted communicationdistance, and store the determined location of the first node aslocation data on the memory storage.

Adjusting the communication distance by the processing unit may beaccomplished as described above with regard to step 3210 of method 3200.And as mentioned above, the processing unit may be further operative toadaptively adjust the communication distance where other types ofcontext data are also considered, such as movement and anticipated nodemovement as detailed out above.

In a further embodiment, the network device may be a mobile master nodethat includes location circuitry (such as GPS circuitry 475 of exemplarymaster node 110 a shown in FIG. 4). In this embodiment, the processingof the network device may be further operative to determine a locationof the network device based upon an output signal from the locationcircuitry received by the processing unit, and determine the location ofthe first node based upon the adjusted communication distance and thelocation of the network device. As such, the first type of the contextdata related to the proximate environment of the first node is basedupon the determined location of the first node.

Those skilled in the art will also appreciate that in some operationalenvironments, the signal degradation information may not require anyadjustment to the communication distance in an embodiment. However, inother environments (e.g., adverse RF environments), the signaldegradation information may provide a basis for adjusting thecommunication distance in the embodiment, even if not performed everytime. Thus, an adjustment to the communication distance may not beneeded in all proximate environments of the first node but may beperformed, if needed, based on the proximate environment of the firstnode. It is the ability of an embodiment to adjust this communicationdistance when needed and if needed that advantageously allows forlocating the first node with more accuracy.

Location Through Triangulation

In some embodiments, various methods for determining a node's locationmay rely upon, at least in part, triangulation techniques. In otherwords, as the wireless node network collects data onreceiver-transmitter pairs, other methods for determining location ofthe individual nodes that utilize triangulation, at least in part, maybecome possible. FIG. 15 is a diagram illustrating an exemplary locationdetermination through triangulation within a wireless node network inaccordance with an embodiment of the invention. Referring now to theillustrated embodiment of FIG. 15, three exemplary master nodes M1-M3910 a-910 c are shown with each master node having a known location.Exemplary ID nodes A-E 920 a-920 e are also shown where they are atleast in communication range of one or more of exemplary master nodesMA-M3 910 a-910 c.

In this illustrated example, the master nodes M1-M3 may detect andcollect advertising messages from ID nodes A-E at varying and knownpower levels. The captured information is forwarded by the master nodesM1-M3 to the backend server 100, where location determinations may bemade. For example, factors like RSSI and visibility of each node at eachpower level may be used to determine, with a higher degree of accuracy,the location of nodes where sufficient information is available.

For an exemplary system to triangulate a node, three nodes with knownlocations must have seen the broadcasting node. In this example, twoadvertising ID nodes, A 920 a and B 920 b, were seen by the three nodeshaving known locations (master nodes M1-M3 910 a-910 c). Based upon thecaptured information, the locations of ID node A 920 a and ID node B 920b are calculated.

Chaining Triangulation

In another embodiment, a node with an inferred location may be used withtriangulation techniques to determine a location of another node in awireless node network. FIG. 16 is a diagram illustrating an exemplarylocation determination through chaining triangulation in accordance withan embodiment of the invention. The locations of ID nodes A 920 a and B920 c have been determined by triangulating across master nodes M1-M3,as illustrated in the exemplary embodiment shown in FIG. 15. However, asillustrated in FIG. 16, the location of ID node C 920 c may also bedetermined according to an embodiment.

For example, an exemplary method of determining a node's locationthrough chaining triangulation begins with determining the calculatedlocation of ID node B 920 b (as explained with reference to FIG. 15).Next, a node closer to ID node B 920 b may be used to get the missingthird signal point needed for triangulation. This may be accomplished byplacing ID node B 920 b in a query (scan) mode such that it listens fora message from ID node C 902 c. ID node C is instructed to advertise,thus providing a signal that may be captured by ID node B. Aftercapturing the signal profile of C, ID node B may communicate or sharethe captured information and forward it along to the backend server 100through either of the master nodes M1 or M2. The resulting locationdetermination of ID node C 920 c may have a higher level of positionerror due to it being partially based on a calculated reference (e.g.,the location of ID node B), but the leveraged location determination ofID node C 920 c may be sufficiently accurate (or be an actionablelocation) that useful information may be gleaned about ID node C 920 c.For example, a leveraged or chained location determination of ID node Cmay indicate, with the help of context data, that nodes M1, M2, and IDnode B are all close enough to ID node C that ID node C is determined tobe within the same container nodes M1, M2, and ID node B.

Location Through Proximity to Triangulation (LP2T)

In an embodiment where chaining triangulation may determine locationthrough proximity to triangulation (LP2T), a starting point may bedetermining the relative location of an ID node to a master node basedon the proximity method, as explained above. However, when the relativelocation of the ID node has been determined, a more accurate or refinedlocation of the ID node may be determined based upon the location of allmaster nodes that can capture the RF output signal broadcast from the IDnode, and then triangulating based on observed signal strength of the IDnode. In this example, the proximity-based location is used as an inputin the triangulation calculation to estimate likely signal deteriorationhistorically observed between a node at the proximity-determinedlocation and scanning master nodes. In a further embodiment, by takinginto account historic data on patterns of signal deterioration, a moreaccurate triangulation may be possible, leading to a more accuratelocation determination.

FIG. 33 is a flow diagram illustrating an exemplary method fordetermining a node location using chaining triangulation for one of aplurality of nodes in a wireless node network having a server inaccordance with an embodiment of the invention. Such an exemplary nodelocation need not be precise or exacting, but can be sufficientlyaccurate without absolutes.

Referring now to FIG. 33, method 3300 begins at step 3305 with theserver receiving a location of a first of the nodes from the first node.Next, at step 3310, the server receives a location of a second of thenodes from the second node. For example, with reference to the exampleshown in FIG. 16, master nodes M1 910 a and M2 910 b may transmit theirrespective location coordinates from their respective onboard locationcircuitry to the server so that the server has the current locations ofthese two master nodes.

At step 3315, the server infers a location of a third of the nodes. Forinstance, in the example illustrated in FIG. 16, the server may inferthe location of ID node B 920 b. In one embodiment, inferring maycomprise having the server determine a proximate-based location of thethird node relative to another of the nodes having a known location,such that the proximate-based location operates as the inferred locationof the third node.

In another embodiment, inferring the location of the third node maycomprise having the server determine a relative location of the thirdnode to the first node (as the node having a known location) or to thesecond node (as another node having a known location). Method 3300 mayalso, in another embodiment, include having the server adjust theinferred location of the third node to determine a refined location ofthe third node based upon third node context data related to theinferred location of the third node

At step 3320, method 3300 concludes with the server triangulating thelocation of the one node based upon determined distances to each of thefirst and second nodes, and a determined distance of the one node to theinferred location of the third nodes.

In a more detailed embodiment, method 3300 may triangulate the locationof the one node by accessing first node context data related to acontextual environment near the first node and second node context datarelated a contextual environment near the second node. Such contextualenvironments may include an environment of being on a conveyor system,or within a particular facility, or next to materials that may degradeor shield signals being received by the one node. Next, the moredetailed triangulating may have the server adjust the determineddistance of the one node to the location of the first node based uponthe first node context data to provide a refined distance of the onenode to the location of the of the first node. Then, the server maytriangulate the location of the one node based upon the adjusteddetermined distance of the one node to the location of the first node,the adjusted determined distance of the one node to the location ofsecond node, and a determined distance of the one node to the refinedlocation of the third node.

In a further embodiment, method 3300 may also have the servertransmitting an instruction so as to cause the server to transmit aninstruction to cause the one node to broadcast a plurality ofadvertising signals over a period of time. In such an embodiment, thedetermined distance of the one node to the location of the first nodemay be based upon captured signals from the one node by the first nodeover the period of time and reported to the server by the first node. Inanother embodiment, the determined distance of the one node to thelocation of the second node may be based upon captured signals from theone node by the second node and reported to the server by the secondnode.

In still another embodiment, the server may transmit an instruction tocause the one node to broadcast a plurality of advertising signals atdifferent power levels. In such an embodiment, the determined distanceof the one node to the location of the first node may be based uponcaptured signals from the one node by the first node and reported to theserver by the first node. In another embodiment, the determined distanceof the one node to the location of the second node may be based uponcaptured signals from the one node by the second node and reported tothe server by the second node.

In yet another embodiment, method 3300 may also have the servertransmitting the location information out to a requesting entity (e.g.,another node, a user access device, etc.) upon receipt of a request fora location of the one node from that entity.

Those skilled in the art will appreciate that method 3300 as disclosedand explained above in various embodiments may be implemented on aserver (such as exemplary server 100 as illustrated in FIG. 5) runningone or more parts of a control and management code (such as an code 525)to implement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium (such as memorystorage 515 in an exemplary server). Thus, when executing such code, aprocessing unit of the server (such as unit 500) may be operative toperform operations or steps from the exemplary methods disclosed above,including method 3300 and variations of that method.

A server apparatus is also described in an embodiment for determining alocation using chaining triangulation for one of a plurality of nodes ina wireless node network. The server apparatus generally comprises aserver processing unit, a server volatile memory, a server memorystorage, and a communication interface. The server volatile memory,server memory storage, and communication interface are each configuredin the apparatus as coupled to the server processing unit. The servermemory storage maintains at least a program code section and locationdata related to nodes in the network. In some embodiments, the servermemory storage may also maintain context data, such as first nodecontext data and second node context data. The communication interfaceprovides a communication path operatively coupling the server with nodesin the network, such as a first and second node.

The server processing unit, when executing at least the program codesection resident in the server volatile memory, is operative to performvarious functions, such as the functions described in the steps aboverelated to method 3300. In particular, the server processing unit isoperative to receive a request over the communication interface for thelocation of the one node. Based on the request, the server processingunit is then operative to receive the respective locations of the firstand second nodes, and store the locations as part of the location datakept on the server memory storage. The server processing unit is furtheroperative to infer a location of a third of the nodes, and store theinferred location of the third node as part of the location data kept onthe server memory storage. The server processing unit then is operativeto triangulate the location of the one node based upon a determineddistance of the one node to the location of the first node, a determineddistance of the one node to the location of second node, and adetermined distance of the one node to the inferred location of thethird node. And finally, the server processing unit is operative totransmit the location information to the requesting entity over thecommunication interface in response to the request.

In one embodiment, the server processing unit may be further operativeto infer the location of the third of the nodes by being operative todetermine a proximate-based location of the third node relative toanother of the nodes having a known location, where the proximate-basedlocation operates as the inferred location of the third node.

In another embodiment, the server processing unit may be furtheroperative to transmit an instruction over the communication interface tocause the one node to broadcast a plurality of advertising signals overa period of time. In this embodiment, the determined distance of the onenode to the location of the first node may be based upon capturedsignals from the one node by the first node over the period of time andreported to the server by the first node. Alternatively, the determineddistance of the one node to the location of the second node may be basedupon captured signals from the one node by the second node and reportedto the server by the second node.

In another embodiment, the server processing unit may be furtheroperative to transmit an instruction over the communication interface tocause the one node to broadcast a plurality of advertising signals atdifferent power levels. In such an embodiment, the determined distanceof the one node to the location of the first node may be based uponcaptured signals from the one node by the first node and reported to theserver by the first node. Alternatively, the determined distance of theone node to the location of the second node may be based upon capturedsignals from the one node by the second node and reported to the serverby the second node.

In yet another embodiment, the server processing unit may be furtheroperative to infer the location of the third node by being operative todetermine a relative location of the third node to the first node or,alternatively, to the second node.

In still another embodiment, context data may be relied upon to refinelocations. More specifically, the server processing unit may be furtheroperative to adjust the inferred location of the third node to determinea refined location of the third node based upon third node context datarelated to the inferred location of the third node.

In a more detailed embodiment, the server memory storage may furthermaintains context data, and the server processing unit may be furtheroperative to triangulate by being operative to access first node contextdata as part of the context data maintained on the server memorystorage, where the first node context data is related to a contextualenvironment near the first node. Likewise, the server processing unitmay be further operative to access second node context data as part ofthe context data maintained on the server memory storage, where thesecond node context data is related a contextual environment near thesecond node. The server processing unit may then be operative to adjustthe determined distance of the one node to the location of the firstnode based upon the first node context data to provide a refineddistance of the one node to the location of the of the first node. Assuch, the server processing unit may be operative to triangulate thelocation of the one node based upon the adjusted determined distance ofthe one node to the location of the first node, the adjusted determineddistance of the one node to the location of second node, and adetermined distance of the one node to the refined location of the thirdnode.

Combined Methods for Determining Node Location

In light of the examples explained above for locating a node, oneskilled in the art will appreciate that a further embodiment expresslycontemplates using more than one of the above-described locationdetermination techniques when determining a refined location of a nodein a wireless node network. For example, such combination embodimentsmay apply an ordered or prioritized approach whereby a first locationtechnique is applied to generate first location information regardingthe location of a node in the wireless network. Thereafter, a secondlocation technique may be selected from a hierarchy or prioritized setof techniques (some of which may work better in certain circumstancesand be chosen or dynamically prioritized based upon the contextualenvironment), and applied to generate second location informationregarding the location of the node or refining the location of the node.Other embodiments may apply additional location techniques to generatefurther refined location information.

In an embodiment, the information in the exemplary hierarchy generallyidentifies which technique may be preferred to be used initially as wellas a ranked grouping or listing of when to apply other locationtechniques. Such information in the exemplary hierarchy may be fixed(based upon successful historic data and experience) or be dynamicallyaltered over time as nodes may move relative to each other and, forexample, based upon context data that provides more information relativeto the a current or anticipated contextual environment.

Applying Node Location Determination in a Vehicular Environment

The various exemplary methods and techniques described above fordetermining the location of a node provide an advantageous way to locatea node. However, further embodiments may advantageously apply suchmethods and techniques in a vehicular environment when dealing withlogistics operations where a node is to be located in a vehicle, movedwithin a vehicle, or removed for delivery from a vehicle.

Essentially, embodiments may use a package enabled with a node(generally referred to as a node package or node-enabled package) toship one or more items and such a node package may be advantageouslyplaced, located, moved, or removed for delivery in avehicle/transportation/shipping/logistics environment. As explainedthroughout this description, a node package is generally a package to beshipped that is related to a particular node. The node and the relatedpackage travel together as part of the shipping process. In a generalembodiment, the node may simply be within the package. In anotherembodiment, the node may be attached to the package (e.g., adhered to aninterior portion of the package, fixed to a part of the package whereone or more status indicators of the node may be visible through thepackage, etc.). In another embodiment, the node of the node package maybe part of the package or the packaging materials used to comprise anexterior, interior, or separating/cushioning material within the nodepackage. In more detail, the node may be integrated as part of thepackage or packaging materials (e.g., integrated as part of a pallet, aULD container, a corrugated fiberboard box, and the like). In stillanother detailed embodiment, the node of the node package may be fullyor partially embedded within the package or packaging materials used tohelp form a general container, which maintains an item to be shippedalong with the node. As explained herein, FIGS. 75A, 75B, 76-78 providevarious illustrations of different exemplary node-enabled packagingmaterials that may be used as part of a node package.

FIG. 93 is a diagram illustrating exemplary node packages located in anexemplary vehicle environment in accordance with an embodiment of theinvention. Referring now to FIG. 93, exemplary vehicle 9300 isillustrated as an example of a general mobile logistics transport orconveyance carrying packages being shipped. Those skilled in the artwill appreciate that vehicle 9300 may be implemented as various types oflogistics conveyances (e.g., automobile, delivery van, autonomousvehicle, truck, trailer, train, aircraft, marine vessel (ship), etc.).Within exemplary vehicle 9300, packages may be placed, stored, andorganized within different storage devices or units, such as storageunit A 9305 or storage unit B 9310. In general, a storage device or unithelps to maintain one or more packages in a configuration that helps toassure save shipment, minimize damage to the packages, and provide a wayto organize what is being stored. Different embodiments of a storageunit may store a single package or may storage a wide variety ofdifferent types of packages that use different types of packagingmaterials (e.g., corrugated fiberboard boxes, wooden and non-woodenpallets, containers, etc.) and in large numbers.

Vehicle 9300 includes a vehicle master node 9315—an exemplaryimplementation of a master node, such as master node 110 a shown anddescribed with respect to FIG. 4. Vehicle master node 9315 is shownoperative to communicate with server 100 over a longer-rangecommunication interfaces (such as interface 485 on exemplary master node110 a) and operative to communicate with other nodes, such as masternode 9320 associated with storage unit A 9305, master node 9325associated with storage unit B 9310, and other nodes associated withparts of such storage units and node packages stored within the storageunits. In more detail, each storage unit may include, in someembodiments, built-in nodes associated with particular shelves, lockers,receptacles, or other parts of the particular storage unit.

Thus, an exemplary storage unit (such as storage unit A 9305) may be anode-enabled storage unit used within a logistics vehicle to safely andintelligently transport node packages. As such, the exemplary storageunit may itself have a hierarchy of nodes (e.g., a master node, and oneor more other nodes (ID nodes or other master nodes) assigned todifferent parts of the unit) and be operative to detect the location ofparticular node packages via the various location determination methodsdiscussed herein as the node package is placed in a storage locationwithin the unit, moved between storage locations of the unit or betweendifferent units, or simply removed from the storage location within theunit.

As shown in FIG. 93, various node packages 9330 a-9330 d may be kept indifferent storage locations of storage unit A 9305 within vehicle 9300.Similarly, other node packages 9330 e-9330 g are kept in portions ofstorage unit B 9310. Such node packages may be placed into particularstorage locations according to shipping information related to the nodepackages. For example, the node packages may be placed into particularstorage locations according to weights of the particular node packages,a planned loading scheme (such as according to an anticipated deliveryschedule), to storage capacity of the particular different locationswithin the storage unit, or according to a storage type for theparticular different locations (e.g., one location for storing envelopetypes of packages, another location for storing boxed container type ofpackages, another location for storing containerized packages (e.g.,ULDs), etc.).

Shipping of containerized groups of packages (e.g., ULD types ofcontainers made to optimize airborne logistics handling of packages) isan example of where a mobile storage unit (such as a movable unit loaddevice (ULD)) may be deployed when shipping node packages in an airborneenvironment. FIG. 94 is a diagram illustrating exemplary mobile storageunits, such as ULDs, used as containers that help ship node packages inan exemplary airborne environment in accordance with an embodiment ofthe invention. Referring now to FIG. 94, a cut-away perspective view ofan exemplary aircraft fuselage 9400 is illustrated. In particular, anexemplary floor 9405 of a cargo storage area within fuselage 9400 isshown having multiple roller elements that help facilitate movement ofcargo within the cargo area. Additionally, while not shown in FIG. 94,the cargo storage area and floor 9405 typically include structure andfastening points to help hold any cargo loaded within fuselage 9400. Thecargo storage area within exemplary fuselage 9400 may be split into anupper area and a lower area by an additional floor 9410.

The cut-away perspective example illustrated in FIG. 94 shows a lowercargo area where various ULD containers 9420 a-9420 d are shown alongwith an airborne master node 9415, which is (depending on the aircraft'slocation and communication mode and status) operative to communicatewith server 100—much like vehicle master node 9315 does as shown in FIG.93. In general, the illustrated configuration of ULD containers 9420 a-dis used similar to the storage units illustrated and described in FIG.93. For example, each ULD container 9420 a-d may have different storagelocations within it and one or more master nodes (not shown) dedicatedand attached internally so that they may track, monitor, and communicatewith different node packages loaded within the ULD as well as othernodes and a server—much like the master node 9320 for storage unit A9305 can track, monitor, and communicate with different node packagesloaded within the storage unit as well as other nodes and server 100.Node packages within each ULD may communicate with nodes in the ULD andmay communicate directly with airborne master node 9415 directly (orindirectly through other master nodes within the ULD). And as such,shipping information may be used when the node packages are placed intoparticular storage locations within a particular ULD according toweights of the particular node packages, a planned loading scheme forthe ULDs (such as according to an anticipated delivery schedule), tostorage capacity of the particular different locations within the ULD,or according to a storage type for the particular different locations.

In light of the exemplary vehicular environments shown in FIGS. 93 and94 showing structure used when initially placing, storing, maintaining,locating, moving, and eventually removing a node package for delivery,those skilled in the art will appreciate that each of the embodimentsdescribed above related to methods for locating a node may be furtherenhanced when applied to an exemplary vehicular environment. Forexample, in one embodiment, determining a node's location may furthercomprise determining a location of the node-enabled package within avehicle to be the location of the node. In a more detailed embodiment,the method that determines a node location may further generate alocation message regarding where the node-enabled package is locatedwithin the vehicle based upon the determined location of the node. Sucha message may be displayed to a user (e.g., logistics personnel thathandle packages being shipped) on a user interface of a node or useraccess device operating as a node (e.g., smartphone or smart wearabledevice). For example, such a displayed message may be a type of aninformed prompt (“Pickup Package X at Storage Location 01 in StorageUnit A”) or strategic instruction (“Place Package X in Storage Location01 in Storage Unit A”) or (“Move Package X at Storage Location 01 inStorage Unit A to Storage Location 03 in Storage Unit B”). In someembodiments, the network device or node that determines the node'slocation may also provide such a display to the user, but in otherembodiments, the location message may be transmitted to another node fordisplay to the user.

In another embodiment, an exemplary method that determines a node'slocation may also access shipping information related to thenode-enabled package and generate a relocation message regarding wherethe node-enabled package may be relocated within the vehicle based uponthe determined location of the node and the accessed shippinginformation. Such a message may be displayed to a user similar to thelocation message described above—namely, that such a relocation messagemay be displayed to a user (e.g., logistics personnel that handlepackages being shipped) on a user interface of a node or user accessdevice operating as a node (e.g., smartphone or smart wearable device)and that in some embodiments, the network device or node that determinesthe node's location may provide such a display to the user, but in otherembodiments, the relocation message may be transmitted to another nodefor display to the user.

In more detail, the shipping information may comprise weight informationon the node-enabled package that is used in determining where torelocate or initially place the node-enabled package.

In another embodiment, such shipping information may be used to create aloading scheme to help organize where to locate or relocate thenode-enabled packages. Thus, the location or relocation of thenode-enabled package within the vehicle may be determined according to aloading scheme. In more detail, such a loading scheme may be related toan anticipated delivery schedule, where the node-enabled package may beplaced within or removed from the vehicle according to the anticipateddelivery schedule.

Logistics Applications of a Wireless Node Network

As described above, an exemplary wireless node network may be useful ina logistics application where an item is to be located. Further, such anexemplary wireless node network may also be useful in logisticsapplications where the item is moving between locations, and the networkprovides an enhanced level of visibility and management of the itemwithin such a logistics environment. In other words, an embodiment of anexemplary wireless node network in accordance with one or moreprinciples of the present invention helps enable enhanced logisticaloperations that manage information when shipping and tracking an item.FIG. 17 is a diagram illustrating an example logistics operation usingexemplary components of a wireless node network in accordance with anembodiment of the invention. FIGS. 34A-34D are additional diagramsillustrating various examples of how different embodiments may also bedeployed at various stages of an exemplary logistics operation.

Logistics Beyond Pickup and Delivery

Referring now to FIG. 17, an ID node 120 a is illustrated as beingdeployed and associated with an item (e.g., package 130) to be shipped.As the package 130 is being prepared for shipping 1700, and is intransit as part of shipment 1705, and is in the possession of theintended recipient 1710, components of an exemplary wireless nodenetwork are deployed to manage information regarding the shipment duringthese three phases.

In a general example of using a wireless node network for managinglogistics related to an item to be shipped, a shipping customer mayinitially register the item (such as package 130) with a node (such asan ID node) to be shipped from an origin location to a destinationlocation. One or more management hand-offs of the item and node occursas the item and the ID node collectively transit a path from the originto the destination. Each hand-off may be based upon an awareness of theshipment path the ID node associated with package 130 will take as it istransferred through a shipping path from its origin to destination.Hand-off of the package 130 and ID node are managed and coordinated withmaster nodes (such as master nodes 110 a-110 h), which are managed byserver 100, along the anticipated shipment path. During operation alongthe shipping path, server 100 receives information and updates fromnodes, manages and authorizes hand-offs between different nodes, andtracks information related to current associations, shared data, sensordata available, locations of the nodes, and context data that helps torefine the location of nodes. Thus, with the ID node associated withpackage 130, the visibility of the package 130 may be extended for thecustomer beyond the conventional custodial control during transit 1705as the shipping customer prepares the item for shipment 1700 prior to aninitial drop-off and after delivery of the item to the recipient 1710.

In a more detailed embodiment, an exemplary method for managinglogistics related to an item to be shipped using a wireless node networkbegins with registering a node with the item to be shipped. For example,the shipping customer may control user access device 200, and use device200 to initially associate an ID node 120 a and package 130 with atracking number as part of preparing to ship the package 130 (a type ofitem). In one embodiment, device 200 may use a particular app or otherprogram module resident and operating on device 200 to input thetracking number of the package 130. Device 200 then provides thatinformation back to server 100 via network 105 to associate the trackingnumber with the package 130 and ID node 120 a. Device 200, in someembodiments, may then print a label for the shipment of package 130 (andID node 120 a). In another embodiment, ID node 120 a may be apreprogrammed node with pre-existing shipping and payment relatedinformation associated with it. Further details of a label-less shippingand payment in another embodiment are described below.

Concurrent with this action, the shipping customer may associate ID node120 a with package 130. For example, the shipping customer may place theID node 120 a within package 130 and, in some cases, physically attachthe ID node 120 a to a particular part of package 130. In anotherexample, the shipping customer may place an exterior label on package130 where the label itself includes ID node 120 a. Other examples mayeffectively group ID node 120 a with package 130 within a largerpackage, container, or pallet of items or packages that collectivelytravel together.

In this manner, device 200 may operate as a type of master node undercontrol of the app or other program module, and be associated with thepackage 130 and ID node 120 a from an association managementperspective. For example, device 200 may operate via the app or otherprogram module along with Bluetooth® hardware and software working ondevice 200 to communicate with ID node 120 a. Other embodiments may relyon other short-range communication interfaces for device 200 tocommunicate with ID node 120 a. And in one embodiment, device 200 mayreceive one or more security credentials from server 100 in order toconnect and actively pair or connect with ID node 120 a.

With at least the shipping information at the server 100, server 100 maydetermine a predicted shipping path for the package 130. In oneembodiment, server 100 may have historic data indicating an optimalroute for shipping an item from point A to point B that uses aparticular shipping path (e.g., pick-up near A by a particular courier,transport by vehicle to a particular facility, further transport viaaircraft to another facility near point B, and transport by vehicle tofacilitate delivery by a courier at point B). In one example, thepredicted path may only be for a portion of the route between twopoints, such as an origin point and a destination point.

In a further example, the predicted path (or part thereof) may beadjusted based on the contextual environment of an item being shipped.For instance, depending on context data (such as weather information,historic data on success for particular transit segments, capacityinformation for third party carriers, etc.), server 100 may alter theinitially predicted shipping path to provide a refined predictedshipping path that is more optimized under the current conditions andcontext. This allows the server 100 to further anticipate which masternodes may be used along an anticipated shipping path (or refinedshipping path), to help efficiently manage shipment of the package 130to point B. Those skilled in the art will further appreciate that anembodiment may only partially identify what master nodes may be usedalong the anticipated shipping path (or refined shipping path), and thatfurther master nodes may be identified as the package 130 is actively inroute to point B depending on context data (e.g., master nodeavailability, weather information, etc.).

In a more detailed example, server 100 may use sort data analytics topredict an appropriate shipping path along which the package 130 and theID node 120 a will travel, identifying predicted master nodes the IDnode 120 a will be within range of during its journey. In the exampleflow illustrated in FIG. 17, nodes 110 a-110 h refer to different masternodes along an exemplary predicted shipping path, which includes atleast a pick-up and drop-off of ID node 120 a and package 130 at anorigin and destination, respectively.

In one example, the shipping customer may place package 130 and itsassociated ID node 120 a in a drop box or repository for items to beshipped. In the illustrated example of FIG. 17, drop box is representedas drop node 110 a. Essentially, drop node 110 a may be implemented witha type of master node connected to or integrated into a drop box orlocker unit type of logistics repository (more generally referred toherein as a node-enabled logistics receptacle). As the shipping customerphysically places ID node 120 a into drop node 110 a, device 200 mayhand-off ID node 120 a to drop node 110 a, update server 100 with thisassociation information, and disassociate from ID node 120 a. In thismanner, the system has visibility into the status and location of anitem (such as package 130) prior to pick-up from drop node 110 a.Further details of an exemplary node-enabled logistics receptacle aredescribed below.

At the drop node 110 a, a courier may pick-up the package 130 and IDnode 120 a. The courier has a courier node 110 b, which knows thetracking number and associated ID node 120 a at time of pickup, or looksup the ID node 120 a MAC address based on a captured tracking number(part of information broadcast or advertised by ID node 110 a.Basically, the master node responsibility transfers to or is otherwisehanded off to courier node 110 b, which now acts as a master nodeactively connected and associated with ID node 120 a (by virtue ofcommunications from courier node 110 b back to server that authorizesthe association of ID node 110 a with courier node 110 b anddisassociates drop node 110 a with ID node 110 a).

Similar handoffs occur between different master nodes and ID node 120 aoccur as package 130 and ID node 120 a transit the anticipated shippingpath in accordance with instructions sent to different master nodes byserver 100. In one embodiment, associations are accomplished during suchhandoffs with security credentials requested, authorized, andtransmitted to the appropriate master node. In another embodiment,associations are merely passive associations that do not require activeand authorized pairings. Yet, the passive association still may allowthe system to keep track of ID node 120 a and package 130 as theytransit the anticipated shipping path.

New associations (active and passive) and disassociations are updated toserver 100. And server 100 may change programming in different nodes aspackage 130 and ID node 120 a transit the shipping path—such as changingthe operation of a master node (such as ULD node 110 e) to shift tooperating as an ID node while airborne or when GPS signals are lost. Inanother example, certain mobile types of node may have responsibilitieschanged to wired types of nodes as a way of preserving the power of amobile type of node. If ID node 120 a fails to associate for a certaininterval and needs to be reacquired, ID node 120 a may update its statusflag to a particular Alert Stage and may attempt to communicate with anincreasingly broader range of master nodes in order to be found.

During the transit, server 100 may share information with differentnodes, such as context data, timer/clock data, environmental data, etc.Sensor data from the ID node 120 a may be gathered via scans from amaster node, and then forwarded back to server 100. And as server 100manages the associations, handoffs, and information going to and comingfrom ID node 120 a (via master nodes), server 100 is able to determinethe location of ID node 120 a using one or more of the various locationdetermination techniques described above. As such, server 100 is able toprovide information related to the ID node 120 a and its related package130 in response to requests for such information.

When package 130 and ID node 120 a arrive at the destination (e.g.,point B), courier node 110 h may update server 100 once ID node 120 a isplaced at the destination and disassociated with courier node 110 h.However, visibility need not end at such a drop-off event (such asarriving at the destination). The recipient customer's user accessdevice 205 may act as another master node, and associate with ID node120 a after delivery. In one example, server 100 is notified by couriernode 110 h that delivery has been made. Thereafter, server 100 maynotify device 205 with this information. In response, an app or otherprogram module on device 205 may cause device 205 to operate as a nodeand to actively seek association with ID node 120 a. When device 205 andID node 120 a connect and are given authorization by server 100 toactively associate, server 100 is notified and may provide furtherinformation to device 205 (e.g., sensor data, etc.) and may be able todetermined updated location data about ID node 120 a and package 130after delivery has occurred. In another example, active association maynot be needed between device 205 and ID node 120 a as status informationmay still be gathered by device 205 via passive association, where thestatus information provides further visibility regarding the ID node 120after delivery to the destination.

FIGS. 18 and 19 are flow diagrams illustrating various exemplary methodsfor managing a shipment of an item using a wireless node network, suchas that illustrated in FIG. 17. Referring now to FIG. 18, exemplarymethod 1800 begins by transmitting shipping information to the server toregister the ID node and the item to be shipped at step 1805 andassociating the ID node to a first master node related to a predictedpath for shipping the item at step 1810. At step 1815, the server isupdated to reflect the association between the ID node and the firstmaster node. Typically, this may come in the form or a communicationfrom the first master node to the server. When the first master node isa user access device (e.g., one of a laptop computer, a desktopcomputer, a tablet device, a personal area network device, a smartphonedevice, and a smart wearable device) that is operated by a shippingcustomer, the server may be updated to become aware that the ID node isassociated with the first master node prior to a pick-up event in thepredicted path.

For example, a shipping customer may use their smartphone to entershipping information and register that the ID node and the item (such aspackage 130) are to be shipped from an origin point to a destinationpoint. Prior to when the item and ID node are picked up by an initialcourier (e.g., from a drop box, locker unit, or other receptacle), theshipping customer's smartphone operates as the first master node and isassociated with the ID node. As such, and with an update to the server,the server now has visibility into the status and location of the IDnode prior to a pick-up event in the predicted shipping path from theorigin point to the destination point.

The method 1800 may continue at step 1820 by disassociating the ID nodeand the first master node when associating the ID node and a secondmaster node related to the predicted path as the ID node transits thepredicted path. In one example, the ID node need not disassociate withthe first master node commensurate with associating with the secondmaster node. Thus, those skilled in the art will appreciate that the IDnode may be associated with one or more master nodes at a given point intime and may be selectively disassociated with certain master nodesdepending on the need for the ID node to securely share data withdifferent master nodes.

At step 1825, the server is updated to reflect the disassociationbetween the ID node and the first master node (if that has occurred yet)and the association between the ID node and the second master node asthe ID node continues to transit the predicted path. At step 1830, themethod may associate the ID node to a third master node near an end ofthe predicted path for shipping the item, and then at step 1835 notifiesthe server to reflect the association between the ID node and the thirdmaster node.

In the method 1800, associating the ID node to the third master node instep 1830 may be performed after a drop-off event in the predicted path.The method may also rely upon context data to adjust for anenvironmental aspect of the predicted path when associating the ID nodeto any of the first, second, or third master nodes.

For example, after the item and ID node are delivered to or near thedestination, the recipient's smartphone may operate as the third masternode associated with the ID node. Data, such as sensor data, may beshared with the recipient while the recipient's smartphone operates asthe third master node associated with the ID node. As such, and with anupdate to the server, the server now has visibility into the status andlocation of the ID node after a drop-off event.

Thereafter, the recipient may unregister the ID node and item given theitem is now in the recipient's possession and control. For example, therecipient may remove the ID node from the item (e.g., the package 130),deactivate the ID node to otherwise power down the device, update theserver regarding the deactivated status of the ID node (and thedisassociation of ID node and the third master node), and then clean upand/or recharge the ID node for future use in shipping another item.

Method 1800 may also include receiving context data related to thepredicted path. In one embodiment, such context data may advantageouslyallow for adjustments due to one or more environmental aspects of thepredicted path when associating the ID node to any of the master nodes.For example, the context data may include scan data indicating the typeof material in package 130 (the item), which may cause RF shieldingissues with the ID node.

Referring now to FIG. 19, exemplary method 1900 is explained from theperspective of the server, which can authorize certain types of nodeassociations. The server may be updated, in some embodiments, withassociation information when an ID node and a master node are passivelyassociated. In such a situation, the nodes have not established anauthorized association where they can securely share data. However, asmethod 1900 explains in more detail, an embodiment may manage a shipmentof an item when active associations are established.

Method 1900 begins with the server receiving shipping information toregister the ID node and the item to be shipped in step 1905. The method1900 then provides a first set of authentication credentials (e.g.,security pin information) to a first master node to permit the ID nodeto associate with the first master node related to a predicted path forshipping the item at step 1910. In one example, the first master nodemay be a user access device, such as a laptop computer, a desktopcomputer, a tablet device, a personal area network device, a smartphonedevice, or a smart wearable device. And step 1920 may be performed priorto a pick-up even in the predicted path.

At step 1915, the server receives an update to reflect the associationbetween the ID node and the first master node. The method 1900 thenprovides a second set of authentication credentials to a second masternode to permit the ID node to associate with the second master node anddisassociate the ID node from the first master node as the ID nodetransits the predicted path at step 1920. At step 1925, the server thenreceives an update to reflect the association between the ID node andthe second master node as the ID node continues to transit the predictedpath (or a portion of a predicted path). When the ID node and the firstmaster node disassociate, the server may also be updated.

In some examples, the method 1900 may have the server provide a thirdset of authentication credentials to a third master node to permit theID node to associate with the third master node as the ID node reachesan end of the predicted path for shipping the item at step 1930. In someexamples, this step may be performed after a drop-off event in thepredicted path.

Finally, at step 1935, the server receives a notification that reflectsthe association between the ID node and the third master node. When theID node and the second master node disassociate, the server may also beupdated.

In method 1900, another embodiment has the server providing any of themaster nodes with context data related to an environmental aspect of apart of the predicted path. For example, exemplary context data mayinclude layout data related to a facility in which the ID node is movingbetween master nodes. In more detail, the received context data may berelied upon to adjust for an environmental aspect of the predicted pathwhen associating the ID node to any of the first, second, or thirdmaster nodes.

In still another embodiment, method 1900 may also determining a locationof the ID node based upon association information received by the serverand location information related to at least one of the first, second,or third master nodes.

As previously discussed, the server may predict a transit route from afirst point to a second point along at least a portion of the predictedpath for shipping the item. In one example, the first point is an originand the second point is a destination point with both being identifiedin the shipping information of the item. However in other examples, thefirst and second point along a predicted path may merely be interimpoints without encompassing the originating shipment point or theultimate destination of the item being shipped. Further, another examplemay adjust the predicted path as the ID node transits the path. In thisway, the server may adapt based upon, for example, context data, so asto optimize or at least account for a changing contextual environmentwhen managing the shipment of an item.

In another embodiment, a non-transitory computer-readable medium isdisclosed that contains instructions, which when executed on a processor(e.g., processor 500 of server 100), performs another embodiment of amethod for managing a shipment of an item using a wireless node networkhaving at least one ID node, a plurality of master nodes, and a server.In this embodiment, the exemplary method begins with the serverreceiving shipping information to register the ID node and the item tobe shipped. The method predicting a first portion of a transit route forthe item from a first point to a second point. For example, a firstpoint may be the origin point and the second point may be thedestination point—both of which are identified in the shippinginformation. In another example, the first and second points are any twopoints along the transit route. Furthermore, the transit route may bepredicted as a series of portions or segments that may use particulartypes of master nodes during transit (e.g., master nodes used by aparticular courier for pick-up, an anticipated vehicle used by thepickup courier, one or more anticipated facilities that may be used bythe vehicle, an anticipated air route (e.g., an anticipated departingairport, an anticipated aircraft, anticipated types of containers suchas a type of ULD or pallet used on the aircraft, and an anticipatedarriving airport), a facility near the anticipated arriving airport, avehicle used to carry the item, and a courier that may deliver the itemat the destination point). Those skilled in the art will realized thatsome of the potential portions of an exemplary predicted path or transitroute may be relatively simple for a local delivery, or may be quitecomplex from an intermodal perspective when the origin point anddestination points are very far away from each other.

Next, the method authorizes a first master node to associate or connectwith the ID node near the origin point. This may be done prior to apick-up event for the ID node and item being shipped. For example, whenthe first master node is a user access device (e.g., a laptop computer,a desktop computer, a tablet device, a personal area network device, asmartphone device, and a smart wearable device) for the shippingcustomer, visibility as to the status and location of the ID node may beextended to prior to a pick-up event. In one embodiment, such anauthorization is performed by the server 100 when it receivesinformation from the first master node regarding the ID node, determinesthat the first master node and the ID node should be actively paired andassociated, and the server 100 sends the appropriate security pininformation as a type of authorization credentials that permit the firstmaster node to actively pair and connect with the ID node. After thefirst master node is associated with the ID node, the server receives anupdate reflecting the association.

Next, the server may authorize a second master node to associate withthe ID node as management responsibility of the ID node is handed offfrom the first master node to the second master node at the second pointon the predicted transit route. In one embodiment, the method mayauthorize the first master node to disassociate with the ID node.However, in other embodiments, the first master node may stay associatedwith the ID node—even after the ID node is authorized to associate withthe second master node. The server then receives an update to reflectthe association between the ID node and the second master node as the IDnode continues on the predicted first portion of the transit route.

The method may further authorize the second master node to disassociatewith the ID node and a third master node to associate with the ID nodeas management responsibility of the ID node is handed off from thesecond master node to the third master node near the destination pointon the predicted transit route. This may be done prior to a pick-upevent for the ID node and item being shipped. For example, when thethird master node is a user access device (e.g., a laptop computer, adesktop computer, a tablet device, a personal area network device, asmartphone device, and a smart wearable device) for the recipient,visibility as to the status and location of the ID node may be extendedto after a drop-off event. After the third master node is associatedwith the ID node, the server receives a notification to reflect theassociation between the ID node and the third master node.

And during the method, the server may determine a location of the IDnode based upon association information received by the server andlocation information related to at least one of the first, second, orthird master nodes. As discussed above, various techniques are availablefor locating a node and, in some cases, adjusting for adverse RFenvironmental conditions with context data to more accurately refine thelocation of a node. As such, the server keeps track of the location ofnodes in the wireless node network, and may provide that information (aswell as other types of shared or sensor information) when requested andauthorized to do so.

From a system perspective of such a logistics application of a wirelessnode network, an exemplary system is disclosed for managing a shipmentof an item using a wireless node network. With reference to FIG. 17, theexemplary system generally comprises an ID node (such as node 120 a), aplurality of master nodes (such as nodes 110 a-110 h), and a server(such as server 100). The ID node is registered to the item (such aspackage 130) being shipped. Each of the master nodes are predicted to belocated at a different part of an anticipated transit route for the itemas the item is shipped from an origin point to a designation point ofthe anticipated transit route. Each of the master nodes is operative tocommunicate with the ID node over a short-range communication path, andoperative to communicate with other master nodes and the server 100.

The server operates to track and report a location of the ID node and alocation of the master nodes. As shown in FIG. 17, server 100 relies onnetwork 105 to communicate with different master nodes (110 a-110 h) aswell as user access devices 200, 205 that may operate and function as amaster node associated with ID node 120 a at certain times. Aspreviously discussed, server 100 may employ a variety of differenttechniques (or a combination of different techniques) for determiningthe location of ID node 120 a or one of the other nodes in the network.

The server is also operative to facilitate the transfer of managementresponsibility of the ID node between different master nodes as the IDnode moves along the anticipated transit route. For example, asdiscussed above, nodes communicate via broadcast and scanning methods,and may be associated under control of the server 100 as part ofmanaging the wireless node network. In this way, a first of the masternodes may be associated with the ID node prior to a pick-up event forthe ID node and item to be shipped. In one example, user access device200 may operate as a master node and be associated with ID node 120 aprior to being placed into drop node 110 a and picked up by a courierfrom the receptacle related to that drop node 110 a.

Later, a second of the master nodes may be associated with the ID nodeafter the ID node is disassociated with the first of the master nodes atan intermediate point of the anticipated transit route. And, a third ofthe master nodes may be associated with the ID node after a drop-offevent for the ID node and item to be shipped. For example, user accessdevice 205 may operate as a master node and be associated with ID node120 a after the ID node 120 a and item are dropped off at an intendeddestination point (e.g., a type of drop-off event).

In an embodiment of the system, each of the master nodes may beoperative to update the server upon completing a disassociation orassociation with the ID node. This provides the server with associationinformation with which it can use to manage and track the nodes in thewireless node network. When associating nodes, the server may beoperative to transmit a set of authorization credentials to one of themaster nodes and the ID node to authorize a desired association betweenthe master node and the ID node. The server may also be operative todetermine the location of the ID node based upon context data, such asinformation relating to an environmental aspect of a part of theanticipated transit path (e.g., RF shielding aspects of the item beingshipped with the ID node or a container holding the ID node, buildinglayout information, etc.).

Those skilled in the art will readily appreciate that operations of suchan exemplary wireless node network, as set forth herein, are not limitedto tracking just a package, but may be used to manage logistics andtracking of other types of items, such as an object or a person. Indeed,some embodiments provide enhanced capabilities that facilitate bettertracking of items, objects, and people as they move to a morerestrictive indoor environment, by using a low power ID node inadvertising mode in the presence of one or more master nodes.

Proactive Shipping Label Generation

While FIG. 17 provides an overview of an example logistics operation aspackage 130 and related ID node 120 a transit a shipping path, FIGS.34A-D illustrate more detailed embodiments of operations at particularstages of an example logistic operation involving shipment of package130 and related ID node 120 a.

In one stage, the shipping customer is dropping off an item to beshipped at a shipping facility. FIG. 34A is a diagram showing anexemplary shipping facility that employs an exemplary wireless nodenetwork to help at this stage. Referring now to FIG. 34A, package 130and related 120 node 120 a are illustrated being taken by a shippingcustomer to a shipping facility 3400 (e.g., such as a FedEx® OfficePrint & Ship Center or the like). In a general example, the shippingcustomer has entered or otherwise provided or registered shippinginformation for an intended shipment of an item and that shippinginformation may be maintained on server 100.

When approaching the shipping facility, the shipping customer mayinteract with a wireless node system for generating a shipping label viaa variety of embodiments of a node associated with the shippingcustomer. In one example, as shown in FIG. 34A, the shipping customermay approach the shipping facility 3400 with the item to be shippedalready in a package 130, which has a node 120 a (e.g., an ID node asillustrated or a mobile master node) in the package 130. In anotherexample, the package 130 may have the node integrated as part of thepackage (generally referred to here as a “node package”).

In another example, the shipping customer may simply approach theshipping facility with a smartphone 200 (a type of user access device)and the item to be shipped but without a package 130 or node 120 a.Here, the smartphone 200 may operate as a type of master node that canuse a longer range communication path to communicate with the shippingfacility's master node 3410 a. Doing so may use a particular app (a typeof programmable code similar to that of code 425). And as the smartphone200 gets closer to the shipping facility, the device may changes modesand operate as a type of ID node (e.g., using a shorter rangecommunication path to communicate with the shipping facility's masternode 3410 a or in a temporary ID node mode that operates without theability to self-locate via GPS when the shipping customer goes insidethe shipping facility). Thus, the node associated with the shippingcustomer may be implemented in a variety of ways—e.g., ID node, masternode, a user access device operating as a type of node—so that theshipping facility can proactively provide an enhanced customerexperience with generating shipping labels, offering packages orspecialized packaging materials, and offering tailored coupons for theshipping customer.

In one example where the shipping customer has already packaged the iteminto a package, prior to arriving at office 3400, the shipping customermay have registered package 130 and ID node 120 a to be shipped from anorigin point to a destination point. For example, the shipping customermay use their smartphone (e.g., a type of user access device 200) and aparticular app (a type of programmable code) operable on that device tofacilitate registration of package 130 and ID node 120 a to be shipped,and to identify a desired drop-off location for the package 130 (and itsrelated ID node 120 a). As the shipping customer travels to the desireddrop-off location (e.g., shipping facility 3400) and approaches thefacility, the system is aware and anticipating the customer's arrival.An office master node 3410 a may detect ID node 120 a and proactivelycause printer 3405 to generate a shipping label 3420 for package 130,and in some cases prompt shipping facility personnel regarding theshipping customer, generate a coupon, prompt the shipping customerdirectly about offers related to their retail experience in the shippingfacility, and the like.

FIG. 35 is a flow diagram illustrating an exemplary method forgenerating a shipping label for an item to be shipped using a wirelessnode network in accordance with an embodiment of the invention.Referring now to FIG. 35, method 3500 begins at step 3505 where themaster node receives shipping information from the server. The shippinginformation is related to the node associated with the shippingcustomer.

As explained above in more detail, the node associated with the shippingcustomer may be implemented in embodiments of method 3500 as an ID node,a master node, a node package, a user access device operating as an IDnode, a user access device operating as a master node, or a master nodeoperating in a temporary ID node mode. And in more detail, the shippingcustomer's master node may be operative to transition how itcommunicates with the shipping facility's master node—namely beingoperative to transition from communicating over a longer rangecommunication path but, when the shipping customer's master node canreceive a signal from the master node associated with the shippingfacility, switching over to communicating over a short rangecommunication path. For example, a shipping customer's mobile masternode (e.g., their smartphone operating an app that enables operation ofthe device as a mobile master node) may use a cellular or WIFI longerrange communication range path as the shipping customer approaches thefacility, and then transition to communicating with the facility'smaster node over a shorter range Bluetooth® communication path when thesmartphone can received a signal from the facility's master node overthat shorter range path.

At step 3510, method 3500 continues with the shipping facility's masternode detecting a signal from the node associated with the shippingcustomer as the node associated with the shipping customer approachesthe shipping facility. In the FIG. 34A example, the signal from theshipping customer's ID node 120 a may be an advertising signal withheader information indicating the ID node 120 a is associated withpackage 130 and may be looking for nodes with which to associate(passively or actively). Once detected, the shipping facility's masternode and the ID node are associated at step 3515.

At step 3515, method 3500 continues by associating the master node andthe node associated with the shipping customer. Such an association mayinvolve establishing a passive association between the facility's masternode and the node associated with the shipping customer withoutrequiring a secure connection between the master node and the nodeassociated with the shipping customer. In another example, such anassociation may involve establishing an active association between themaster node and the node associated with the shipping customer, wherethe active association reflects a secure connection between thefacility's master node and the node associated with the shippingcustomer. And in a further embodiment, method 3500 may have the masternode be operative to update the server with updated association datawhen the master node is no longer associated with the node. In theexample shown in FIG. 34B, office master node 3410 a may still beassociated with ID node 120 a when package 130 is placed withinreceptacle 3415. However, drop node 110 a associated with receptacle3415 may detect and associate with ID node 120 a. And at some point intime, for example with the package 130 has been in receptacle 3415 for aparticular duration or when the package 130 is picked up from receptacle3415 by a courier, office master node 3410 a may disassociate with IDnode 120 a. At that time, other nodes are associated with ID node 120 aand may facilitate tracking and management with server 100.

At step 3520, method 3500 concludes with the facility's master nodecausing the generation of the shipping label for the item to be shipped.This happens when the facility's master node determines the nodeassociated with the shipping customer is within a predetermined range ofa location within the shipping facility. For example, referring to FIG.34B, ID node 120 a (as a type of node associated with the shippingcustomer) and package 130 are now within the shipping facility 3400 andcloser to office master node 3410 a, which may be deployed at a drop offcounter location within the facility 340. As ID node 120 a approachesoffice master node 3410 a at that location or some other designatedlocation within the shipping facility, the location of the ID node 120 awill enter a predetermined range distance from office master node 3410a. At that point, office master node 3410 a may instruct the printer3405 (e.g., via wired or wireless connection) to generate a shippinglabel 3420 for the package 130 to be shipped. In another example, theoffice master node 3410 a may determine the ID node 120 a is within apredetermined range of a shipping department drop off receptacle 3415(e.g., an example of a designated location within the shippingfacility).

In a more detailed embodiment, the location within the facility may be atype of designated points, such a drop off location for the item andnode (e.g., a desk, counter, receptacle, etc.), a generation locationfor the shipping label (e.g., an area near a printer within the shippingfacility), and a pickup location for the shipping label (e.g., a desk,counter, receptacle, etc.).

In a further embodiment, the method 3500 may further include theshipping facility's master node determining that the node associatedwith the shipping customer is within the predetermined range of thedesignated location by instructing the node associated with the shippingcustomer to alter an RF power characteristic (e.g., an RF transmissionpower level) as part of locating the node associated with the shippingcustomer.

In general, an exemplary shipping label accompanies the item beingshipped (and any ID node related to the item, such as ID node 120 awithin package 130). Examples of shipping label 3420 may include a humanreadable label with information, such as a tracking number associatedwith the shipping information, an address associated with the shippinginformation, information about a user shipping the item. And the labelmay also include one or more machine readable references, such as ascannable image (e.g., barcode) or scannable tag (e.g., RFID tag), toattach to the item to be shipped. As shown in FIG. 34B, the generatedshipping label 3420 may be placed on package 130 prior to placement ofpackage 130 (and ID node 120 a) within receptacle 3415.

In still another embodiment, method 3500 may also include updating theserver when the master node is no longer associated with the nodeassociated with the shipping customer. The server may also be updated,in a further embodiment, with location metric information related toanalytics on movement of the node associated with the shipping customerwithin the shipping facility. For example, as shown in FIG. 34A, as theoffice master node 3410 a tracks the ID node 120 a within shippingfacility 3400, the master node may collect, record, and forward locationmetrics (e.g., position, time, movement directions) to server 100 aspart of data analytics quantifying efforts to understand how and wherethe ID node and/or the shipping customer with their smartphone moveswithin the shipping facility 3400. In more detail, the office masternode 3410 a may track metrics related to how long the ID node 120 astays in receptacle 3415 before a courier picks up package 130. In stillanother embodiment, the office master node 3410 a may track metricsrelated to how long it takes to print out certain types of shippinglabels, and use such metrics (by the server or master node) to adjustthe predetermined range distance so that the shipping label is optimallygenerated so to best assist the shipping customer and operations of theshipping facility 3400.

Those skilled in the art will appreciate other sales and shippingrelated logistics metrics may be tracked and uploaded to the server 100,so that server 100 can learn about operations within shipping facility3400 and leverage use of that information as a type of historic datawhen attempting refine locations of nodes being tracked in the future.Thus, the node's movements and tracking information on that within theshipping facility provides a type of data source for analytics to helpthe facility understand the consumer experience—for the shippingcustomer when the node is, for example, the customer's smartphone; orfor a package that is node-enabled and is processed within the shippingfacility.

In another embodiment, method 3500 may have the facility's master nodecausing the generation of one or more additional shipping labels whenthe master node determines the node associated with the shippingcustomer is within a predetermined range of a location within theshipping facility. Thus, the shipping information may indicate the needfor any additional shipping labels and the embodiment allows for theproactive generation of such labels.

In a further embodiment, method 3500 may also proactively provide theshipping customer with one or more coupons as part of their experiencein coming to the shipping facility and interacting with the facility'swireless node network. In more detail, method 3500 may have the masternode cause generation of a coupon for packaging material for the item tobe shipped, or other consumables offered by the facility. Should theshipping customer be determined to be a priority customer (e.g., afrequent consumer of the facility, a designated representative of acorporate client of the shipping facility, or the like), an embodimentmay have the facility's master node generating a notification forshipping facility personnel by the master node prior to generating theshipping label, the notification indicating that the shipping customeris the priority customer

Additionally, certain embodiments may have the facility's master nodeproviding messages to prompt different people. In one example, themaster node may provide a message to a user access device operated byshipping facility personnel, where the message causes the user accessdevice to display a prompt related to offering the shipping customerpackaging material. In another example, the facility's master node maydirectly provide a message to the node associated with the shippingcustomer, where the message causes the node to display a prompt relatedto an offer for packaging material. In still another example, thefacility's master node may provide a message to a user access deviceoperated by shipping facility personnel, where the message causes theuser access device to display a prompt related to offering the shippingcustomer a specialized packaging material for the item to be shippedbased upon a value of the item being shipped as identified in theshipping information. Further still, the facility's master node mayprovide a message to a user access device operated by shipping facilitypersonnel, where the message causes the user access device to display aprompt related to offering the shipping customer a specialized packagingmaterial for the item to be shipped based upon an indication that theitem to be shipped is fragile. As part of such prompting examples,further embodiments contemplate more interactive messages where theshipping customer may be able to, for example, select which type ofspecialized packaging material they want to use, or which type ofcoupons they would like to redeem.

Referring back to the example shown in FIG. 34A, office master node 3410a may interact with the printer 3405 directly or indirectly when causinggeneration of the shipping label in an embodiment. In one example, labelprinter 3405 is directly coupled to office master node 3410 a. However,in another example, the label printer 3405 may be directly connected toanother computer system (e.g., an order management system (not shown)that communicates directly or indirectly with server 100 and helpsfacilitate shipping orders and payment for the same). Thus, while notdirectly connected to office master node 3410 a, office master node 3410a may still be able to communicate and cause the printer 3405 togenerate the label 3420 via indirect connections (e.g., WiFi or wiredLAN connection from office master node 3410 a to the order managementsystem, or network connections from office master node 3410 a to server100, which may communicate separately with printer 3405). Additionally,server 100 may be operative to cause printing to occur on printer 3405.

Those skilled in the art will appreciate that method 3500 as disclosedand explained above in various embodiments may be implemented on anetwork device, such as office master node 3410 a illustrated in FIG.34A, running one or more parts of master control and management code 425to implement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium such as memorystorage 415 on a master node (such as office master node 3410 a). Thus,when executing code 425, the master node's processing unit 400 may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 3500 and variations of that method.

Payment Transactions Using Node Association

In the example shown in FIG. 34B, the shipping label 3420 may be onpackage 130 and the shipping customer may desire to pay for shipping thepackage 180 to its intended destination. In one embodiment, payment maybe facilitated using an association established between nodes. In otherwords, the shipping customer may utilize a node, and based upon anassociation between the customer's node and the payment receiver'smaster node, a payment transaction may be conducted.

FIG. 36 is a flow diagram illustrating an exemplary method forconducting a payment transaction using a node association in a wirelessnode network in accordance with an embodiment of the invention.Referring now to FIG. 36, exemplary method 3600 begins at step 3605 bydetecting, by the master node, a signal from the ID node as the ID nodeapproaches the master node, the master node being related to a paymentreceiver and the ID node being related to a payment provider.

At step 3610, determining, by the master node, if the ID node desires toassociate with the master node for the payment transaction based upon afirst part of the information within the signal. In one embodiment, theinformation within the signal includes header information of a signalbroadcast from the ID node (e.g., a mobile user access device, such as asmartphone 200 of the shipping customer). The header information mayinclude status information on whether the ID node is in a particularstate (e.g., a discoverable advertising state, a general advertisingstate, or a non-connectable advertising state as discussed above withreference to FIG. 8). The information may also include an identificationof a particular consumable (such as a product or service) to bepurchased in the payment transaction, and in another part of theinformation, include an identification of a payment source for thepayment transaction. In the example of FIG. 34B, mobile user accessdevice 200 may broadcast a signal, which is detected by office masternode 3410 a. Part of the information broadcasted in the signal mayidentify the shipment to be purchased (e.g., shipment of package 130).

Another part of the information broadcasted may identify a paymentsource for the payment transaction. This may be a conventional currencybased payment source (e.g., a bank account, a credit account, or thelike) or may be a non-currency type of program (such as a rebateprogram, award point program, or other closed ecosystem type of programused to exchange value for products/services from the payment receiver).For example, the shipping customer may prepay for a desired amount ofshipping credits with a specific shipping company and, in someimplementations, allow integration of an embodiment with conventionalpayment systems such as the Google Wallet app, the Square Wallet app, orPayPal® payment systems. The prepaid shipping credits related to theshipping customer may, in some embodiments, be part of the shippinginformation, and in some cases, can be staged on a node (such as asmartphone 200 operating as an ID node). Staging payment credits with aparticular node helps facilitate other payment services, such ascost-on-delivery (COD) type services. It also allows for a payment stateto be preserved within the node as the package moves through adistribution or shipping network. In some embodiments, the payment statepreserved on the node reflecting present credits may be updated (addedor removed credits) as the node moves through the distribution orshipping network.

At step 3615, the master node associates with the ID node when the IDnode desires to associate with the master node for the paymenttransaction. In one embodiment, associating may involve altering abroadcasting mode of the master node and instructing the ID node toalter its broadcasting mode to enable associating the master node andthe ID node. In another embodiment, associating may involve establishinga passive association between the master node and the ID node withoutrequiring a secure connection between the master node and ID node.However, in yet still another embodiment, associating the nodes mayinvolve establishing an active and secure association between the masternode and the ID node where the active association reflects a secureconnection between the master node and ID node. Such an active andsecure association may be facilitated with preloaded credentials, but inother embodiments such authority to associate may be requested from theserver.

In a more detailed example, the master node may establish the activeassociation with the ID node after receiving an acknowledgement from theID node related to the payment transaction. This acknowledgement may beprompted, in one example, with a displayed prompt on the ID node (e.g.,the screen of the shipping customer's mobile smartphone 200 operating asan ID node for purposes of paying for shipping of the package 130).

Referring back to the example of FIG. 34B, office master node 3410 a mayanalyze the information broadcast in the signal (e.g., a Bluetooth®formatted short range transmission signal) from the mobile user accessdevice 200 operating as an ID node when determining whether to associatewith mobile user access device 200 for this purpose. If the officemaster node 3410 a determines that the mobile user access device 200desires to proceed with a payment transaction related to shipment ofpackage 130 (based upon information in the signal), office master node3410 then associates with the mobile user access device 200 operating asan ID node. For example, the office master node 3410 a may receiveinformation from server 100 related to the shipment of package 130, andknow that the mobile user access device 200 is identified in a profilefor the shipping customer, and that shipping information related topackage 130 is in the system with a charge identified for the service ofshipping package 130. Thus, based upon the shipping information and theprofile information on the shipping customer related to the shippinginformation, office master node 3410 a may only need to associate withthe shipping customer's mobile user access device (e.g., smartphone 200)to proceed and complete the payment transaction for shipping package130.

At step 3620, method 3600 concludes by submitting payment transactiondata to the server. The payment transaction data is based upon anotherpart of the information within the signal broadcast from the ID node(e.g., smartphone 200 in the example of FIG. 34B). In more detail, thepayment transaction data may reflect an authorization to complete thepayment transaction based upon the successful association of the masternode and the ID node.

In one example, server 100 may receive the payment transaction data(e.g., acknowledgement that a successful association occurred for thattransaction) and the server 100 may rely on data already resident in itsserver memory (e.g., related to the shipping information, prices for theshipping order, payment source information provided as part of enteringthe shipping information and initially registering the package 130 andID node 120 a) to then conclude the payment transaction. In anotherexample, the server 100 may receive further information (such as updatedpayment source information) from the ID node (e.g., smartphone 200) aspart of the payment transaction data via the associated master node.

In a further embodiment method 3600 may include steps where the mobileuser access device operating as an ID node provides a user interfacewith displayed prompts as part of validating payment, authenticatingpayment, and a charge notification approval display. One or more promptsmay appear on the user interface of the mobile user access device. Suchprompts typically inform the operative of the device of informationrelated to the transaction, or ask for further input related to thetransaction. In such an embodiment, the operator of the mobile useraccess device may provide one or two-way interaction to approve,validate and otherwise authenticate a payment transaction conductedbetween the nodes.

While many embodiments may rely on authenticated connections whereinformation may be more securely shared for the payment transaction,other embodiments may rely on unauthenticated connections (e.g., passiveassociations or active but not secure or authenticated connections). Assuch, the security aspect may come into play on the backend server thatutilizes proprietary credits rather than conventional currency. Forexample, when a node package is dropped in a node-enabled logisticsreceptacle (such as a drop box), the customer may be automaticallydebited with a preauthorized account with the shipping entity. Theshipping entity's backend server can keep track of the credits and debitthe customer's account accordingly based on the detected deposit of thenode package.

Those skilled in the art will appreciate that method 3600 as disclosedand explained above in various embodiments may be implemented on anetwork device, such as office master node 3410 a illustrated in FIG.34B, running one or more parts of master control and management code 425to implement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium such as memorystorage 415 on a master node (such as office master node 3410 a). Thus,when executing code 425, the master node's processing unit 400 may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 3600 and variations of that method.

Likewise, those skilled in the art will appreciate that in light of themethod 3600 described above and further details described therein, thatan exemplary system of a server and master node associated with apayment receiver (e.g., a FedEx® Office Print & Ship Center) may be usedfor conducting a payment transaction using node association. In thisembodiment, the master node is operative to communicate with the serverand separately detects and is operative to communicate with an ID nodefor purposes of associating for a payment transaction where the masternode's processing unit, when running the code 425, implements the stepsdescribed above related to method 3600.

Node-Enabled Shipping without a Shipping Label

While the embodiment described with respect to FIG. 35 involvesproactive generation of a shipping label for an item to be shipped,another embodiment using a wireless node network in accordance with anembodiment of the invention allows for node-enabled shipping without ashipping label. FIG. 37 is a flow diagram illustrating an exemplarymethod for preparing a node-enabled shipment of an item to be shippedusing a wireless node network in accordance with an embodiment of theinvention. Referring now to FIG. 37, method 3700 begins at step 3705 bycapturing an identification of the node to be related to the item by auser access device. In different embodiments, the node may beimplemented by an ID node, a sensor node, or a master node. In a moredetailed embodiment, the node may be implemented as a mobile master nodehaving at least one sensor onboard the master node for gatheringenvironmental information about an environment near the master node.

For the node to be related to the item being shipped, identification ofthe node may be captured with the user access device (e.g., asmartphone, laptop computer, desktop computer, personal area networkdevice, and the like as described herein) in a various ways. In oneexample, capturing the identification of the node may involve detectingan electronic identification of the node (such as a Bluetooth® signatureor identifier (e.g., MAC address) for the node, a near fieldcommunication (NFC) code related to the node, an RFID identifier relatedto the node). In one embodiment where the RFID version is implementedwith NFC, the user access device may be able to communicate via veryshort range NFC signals to capture the NFC code but then auto-associatethe node using a less range restrictive communication path (e.g.,Bluetooth® Low Energy or BLE). In another example, capturing theidentification of the node may involve viewing a readable identifier ofthe node (such as a written label on the exterior of the node having anidentification printed on the label). In still another example,capturing the identification of the node may involve scanning amachine-readable identifier of the node (such as a barcode).

At step 3710, shipping information is entered into the user accessdevice. The shipping information is related to the item and includes alink between the shipping information (e.g., shipping customer, origin,destination, etc.) and the identification of the node.

At step 3715, the shipping information is stored on the node. Theshipping information may be stored in a node's volatile memory, onboardmemory storage, or both. In one embodiment, the shipping information maybe uploaded to the server. In a more detailed embodiment, the shippinginformation may be transmitted to the server to pre-associate theshipping information for the node with another node (e.g., couriermaster node 110 b shown in FIG. 34A) in the network related to a person(such as a courier) that will handle a logistics transaction for theitem to be shipped. Exemplary logistics transactions may include pickingup the item, dropping off the item, and the like. At pickup, the couriermay optionally generate a shipping label to facilitate further logisticshandling of the item being shipped; however, in other embodiments, nofurther label is needed as the node may communicate the necessaryinformation for successful shipment to other nodes as it transits itspath towards its shipment destination.

At step 3720, the item to be shipped is combined with the node.Typically, the item to be shipped may include a package for the item.The package may help protect the item as it is shipped to a destination.Thus, in one example, the item to be shipped may be combined with thenode by placing the node within an interior of a package for the item tobe shipped. Depending on the item being shipped, those skilled in theart will appreciate that the actual location of the node within theinterior of the package may adversely impact how the node cancommunicate with other nodes.

In another example, the item to be shipped may be combined with the nodeby securely fixing the node to an interior surface of a package for theitem to be shipped. In more detail, the node may be adhered to aside-wall or top interior surface within the package. Keeping the nodein a fixed location proximate to a wall or top of the package my keepthe contents of the package from interfering with the node (orcommunications from the node) and help avoid physical damage to the nodefrom the contents of the package (the item being shipped).

In a further example, the node may be embedded as part of a package forthe item to be shipped. In this example, the node may be integrated intothe package or packaging materials and may be partially or entirelyembedded within the package or packaging materials.

In yet a further example, the item to be shipped may be combined withthe node by securely fixing the node to an exterior surface of a packagefor the item to be shipped. In this example, the node may be implementedin a relatively flat configuration so as to ensure the node stays fixedto the package as the item is shipped to its destination. In particular,the package may have a special location, such as a recessed location,which is accessible from the exterior of the package and where ashipping customer may place and securely fix the node.

In another embodiment, method 3700 may also include fixing an externalnotification to a package for the item to be shipped, the externalnotification providing notice that the package is a node shipment. Theexternal notification in this embodiment is not a shipping label in thatit does not include shipping information viewable on the exterior of thepackage. Instead, an exemplary external notification may display asimple message to alert shipping company personnel that the packageincludes a related node that may (e.g., via scanning, via communicationswith, via indirect passive analysis of signals from the node) be used tohelp track and manage the package as it is shipped without requiring afull shipping label.

Those skilled in the art will appreciate that method 3700 as disclosedand explained above in various embodiments may be implemented on a node,such as an exemplary ID node or sensor node illustrated in FIG. 3, or anexemplary master node as illustrated in FIG. 4, running one or moreparts of their respective control and management code to implement anyof the above described functionality. Such code may be stored on anon-transitory computer-readable medium, such as memory storage withinsuch types of exemplary nodes. Thus, when executing such code, aprocessing unit within the respective node may be operative to performthe operations or steps from the various exemplary methods disclosedabove where the shipping information is received by the user accessdevice and the combining step may be implemented as issuing a message onthe user interface of the user access device to combine the item to beshipped and the node.

Likewise, those skilled in the art will appreciate that in light of themethod 3700 described above and further details described therein, thatan exemplary system of a server and a node may be used for preparing anode-enabled shipment of an item to be shipped using a wireless nodenetwork according to an embodiment. The exemplary node in the system maycomprise a node processing unit, a node memory storage coupled to theprocessing unit, and a communication interface coupled to the processingunit and operative to communicate with a user access device (e.g.,smartphone 200 used by a shipping customer). Examples of the node mayinclude an ID node, a sensor node, and a master node. In a more detailedembodiment, the node may be implemented as a mobile master node havingat least one sensor onboard the master node for gathering environmentalinformation about an environment near the master node.

The exemplary server in the system is operative to communicate with thenode via the communication interface. However, those skilled in the artwill appreciate that if the node is an ID node or sensor node, theserver may separately communicate with the node indirectly through theshipping customer's user access device (operating as a master node)while the user access device communicates with the node through thecommunication interface.

The exemplary node's processing unit is operative to emit anidentification of the node to be related to the item by the user accessdevice. For example, the node may emit or otherwise transmit ashort-range signal that identified the node and that identification maybe related to the item being shipped after it is captured by the useraccess device (e.g., via Bluetooth® Low Energy communications). The nodeprocessing unit is further operative to receive shipping informationfrom a user access device, the shipping information being related to theitem and is linked with the identification of the node. The nodeprocessing unit is further operative to store the shipping informationon the node (e.g., on the node memory storage) when the node and theitem to be shipped are combined for shipping.

The node processing unit may be further operative to upload the shippinginformation to the server. The server, in one embodiment, may beoperative to receive the shipping information from the node (e.g., whenthe node is a master node). In other embodiments, the server may beoperative receive the shipping information from the user access device(e.g., when the node is an ID node or sensor node).

Node-Enabled Logistics Receptacle

In FIGS. 34A and 34B, receptacle 3415 is a drop-box and/or pickup typeof container (more generally referred to as a logistics receptacle) thatmay temporarily maintain custody of items being shipped (along withtheir respective ID nodes should one be present with the particularitem). In some examples discussed here, receptacle 3415 is a simplecontainer or receptacle for one or more packages to be shipped. Theexemplary receptacle has an entrance opening through which an item beingshipped (along with its related node) can pass as the item is depositedwithin a storage area of the receptacle. Thus, the storage areamaintains the item being shipped and the related node after it isdeposited within the receptacle.

In some embodiments, the receptacle may be implemented as a secureaccess receptacle or container (such as a locker type of logisticsreceptacle) having an entrance opening that is accessible to a shippingcustomer for depositing the item to be shipped (and its readable node),but once within the receptacle the item is secure and only removed froma secure storage area within the receptacle by someone with a key orcombination. Such an example of a logistics receptacle may be usefulwhen deployed in situations where personnel are not actively managingthe receptacle.

An embodiment of receptacle 3415 may deploy this receptacle as anode-enabled assembly. In other words, in this other embodiment,receptacle 3415 may have an attached or integrated node (such as dropnode 110 a or ID node 110 a or master node 120 a) as part of theassembly making up receptacle 3415. Equipping the receptacle 3415 withsuch a node (e.g., an ID node, a sensor node, or a master node with orwithout sensors) in an embodiment provides a way to identify items beingshipped that have related advertising nodes with the item as the itemsare left near or deposited in the receptacle (such as a drop box type ofcontainer). The node assembled with the receptacle operates to detectsignals from nodes related to items being shipped. When detected, thereceptacle's node associates with the node related to the item beingshipped and based upon the location of the that node relative to thereceptacle, the receptacle's node may alter a current inventory relatedto the receptacle that is stored in that node's memory storage. As thenode related to an item being shipped (e.g., a node package) approachesthe node-enabled logistics receptacle and is deposited into thetemporary custody of the receptacle, the receptacle's node may instructthe node package to adjust its RF output signal (e.g., adjusting abroadcast profile for the node package). As such, the receptacle's nodetakes advantage of a new package node's communication profile as ithelps facilitate the communication behavior of the new node within thereceptacle's temporary managerial custody so there is less potentialinterference and disruption with communications to and from other nodeswithin the node-enabled logistics receptacle's custody (inside or nearthe receptacle).

Further details on various embodiments of an exemplary node-enabledlogistics receptacle assembly appear in FIGS. 34A-34D, 85A, 85B, 86A,86B, and 89A-89D. In some of these embodiments, the node within thenode-enabled logistics receptacle assembly may include at least onesensor that monitors for a deposited package the custody of which istemporarily maintained by the node-enabled logistics receptacleassembly. As discussed more with respect to FIGS. 89A-89D, such a sensormay be implemented with one or more internal sensors, external sensors,and/or door sensors to help detect packages.

FIG. 38 is a flow diagram illustrating an exemplary method for operationof a node-enabled logistics receptacle in a wireless node network inaccordance with an embodiment of the invention. Referring now to FIG.38, method 3800 begins at step 3805 by detecting a signal broadcast fromthe first node. In the example shown in FIG. 34B, receptacle 3415 may bea node-enabled logistics receptacle where drop node 110 a isincorporated into the assembly having receptacle 3415. As package 130and ID node 120 a approach drop node 110 a embedded in receptacle 3415,drop node 110 a detects a signal broadcast from ID node 120 related tothe package 130 being shipped.

At step 3810, the node-enabled logistics receptacle associates with thefirst node. Back in the example of FIG. 34B, drop node 110 a associateswith ID node 120 a. As ID node 120 a approaches drop node 110 a, dropnode 110 a may instruct ID node 120 a to alter a power characteristic ofits advertising signal (such as the RF output power level) in order toallow the drop node 110 a to better locate the ID node 120 a.

At step 3815, the location of the first node is determined by thenode-enabled receptacle. As a fixed location installation, the physicaladdress of the drop node 110 a may be assumed to be identical to thereceptacle itself. In other embodiments where drop node 110 a is amaster node, the location of the receptacle may not be fixed and dropnode 110 a may have location circuitry with which to determine thenode-enabled receptacle's current mobile location.

In one embodiment, the method may detect if the first node is leftwithin a vicinity of the node-enabled logistics receptacle based on thelocation of the first node. The vicinity of the node-enabled logisticsreceptacle may be an area sufficiently proximate to the node-enabledlogistics receptacle to indicate that an item and node within thevicinity intends to be shipped. For example, the node-enabled logisticsreceptacle may detect that the item (e.g., package 130) and its relatednode (ID node 120 a) are left immediately outside of the node-enabledreceptacle, which may indicate (along with a current inventory) that thenode-receptacle is full and in need of pickup. In one embodiment, thenode-enabled logistics receptacle may send a message to a serverregarding the need for pickup under certain circumstances (e.g., when apredetermined number of nodes are detected in the current inventory orthere is at least one node detected outside the receptacle).

In another embodiment, the method may detect if the first node is withinthe node-enabled logistics receptacle based on the location of the firstnode. Depending on the size of the receptacle, this may be possiblegiven the granularity of possible location determinations. And once thefirst node is detected within the node-enabled receptacle, it is deemeddeposited for shipment and should be counted towards the currentinventory.

At step 3820, the node-enabled logistics receptacle alters a currentinventory of nodes related to the node-enabled logistics receptaclebased upon the location of the first node. In one example, the inventorymay include those nodes in the vicinity of the node-enabled receptacle.In another example, the inventory may only include those nodes detectedto be within the node-enabled receptacle.

The method 3800 may also detect removal of the first node from thevicinity of the node-enabled logistics receptacle and from within thenode-enabled logistics receptacle itself. Thus, the node-enabledlogistics receptacle may be operative to manage a current inventory ofnodes (and related items being shipped) and inform the server of suchinformation. When the node embedded with the receptacle is implementedand operates as an ID node, the embedded node may be able to collectscan results from other ID nodes in the receptacle, and then transferthem to a master node. In other words, the node-enabled logisticsreceptacle is operative to transfer one or more results collected by thenode-enabled logistics receptacle listening to at least one other IDnode within the receptacle. However, if the embedded node is implementedand operates as a master node, the embedded node can directly update aserver when the current inventory of nodes changes.

In another embodiment, when the embedded node (e.g., drop node 110 a) isimplemented and operates as a sensor node having one or moreenvironmental sensors, the processing unit of the embedded node may beoperative to detect an interior condition of the receptacle using theone or more environmental sensors. For example, if the interiorcondition of the receptacle is wet, the embedded node may want toimmediately have the server notified. Thus, once the interior conditionis known, the embedded node may transmit an environmental update on theinterior condition of the receptacle to a master node, which is thenoperative to pass it on to the server.

The method 3800 may also include tracking inventory metric informationas a type of productivity data. In one embodiment, inventory metricinformation about when each of the nodes in the current inventory ofnodes arrive and depart from within the node-enabled logisticsreceptacle is tracked, and the embedded node may cause such inventorymetric information to be sent to the server (e.g., directly transmittingthe information to the server when the embedded node is a master node,or indirectly sending the information to the server via a connectedmaster node when the embedded node is an ID node). Thus, in one example,the inventory metric information may be related to when pickup personneland/or vehicles equipped with nodes arrive and depart at the locationwith the node-enabled receptacle.

In a further embodiment, method 3800 may also help manage RFcommunications of nodes within the custody or soon to be in the custodyof the node-enabled logistics receptacle. Specifically, an embodiment ofmethod 3800 may also comprise instructing the first node by thenode-enabled logistics receptacle to change an output power setting onthe first node to a different power level when the location of the firstnode places the first node in a temporary custody of the node-enabledlogistics receptacle. In more detail, such a step of instructing thefirst node by the node-enabled logistics receptacle to change the outputpower setting on the first node to the different power level maycomprise adjusting a broadcast setting of a broadcast profile for thefirst node. For example, the exemplary method discussed with respect toFIG. 52 and the accompanying description explain how a broadcast settingmay be adjusted as part of a node's broadcast profile that defines how anode communicates.

Those skilled in the art will appreciate that method 3800 as disclosedand explained above in various embodiments may be implemented on a node,such as an exemplary ID node or sensor node illustrated in FIG. 3, or anexemplary master node as illustrated in FIG. 4, running one or moreparts of their respective control and management code to implement anyof the above described functionality. Such code may be stored on anon-transitory computer-readable medium, such as memory storage withinsuch types of exemplary nodes. Thus, when executing such code, aprocessing unit within the respective node may be operative to performoperations or steps from the exemplary methods disclosed above,including method 3800 and variations of that method.

Node-Enabled Packaging

Embodiments of nodes in an exemplary wireless node network may be partof different types of electrical components (such as a coupler connectoras shown in FIG. 55), but may also be advantageously integrated into orotherwise be part of a container (such as a package) commonly used tohold or ship items. One type of container used for shipping an item is acorrugated fiberboard box (also referred to commonly as a “cardboardbox” or “cardboard package”). Among its uses, a corrugated box may beused by manufacturers of products to hold or ship items, such asproducts, to retail distributors or to end users, and used by thegeneral public to ship materials, gifts, or other items to friends andrelatives. When used in such a manner, the corrugated box operates as apackage for the item being shipped.

In general, a package may be enabled with a node (generally referred toas a node package or node-enabled package) when shipping one or moreitems in the package. And as noted, in a general embodiment, the nodemay simply be placed within the package while in other embodiments, thenode may be attached to the package (e.g., stuck or adhered to aninterior portion of the package, fixed to a part of the package whereone or more status indicators of the node may be visible through thepackage, held in place relative to a designated portion of a package,etc.) or may be part of the package or the packaging materials used tocomprise an exterior, interior, base, or separating/cushioning materialwithin the node package. In more detail, the node may be integrated aspart of the package or packaging materials (e.g., built-into a part of abox or pallet structure). In still another detailed embodiment, the nodeof the node package may be fully or partially embedded within thepackage or packaging materials used to help form a general container,which maintains an item to be shipped along with the node. As explainedbelow in more detail, FIGS. 75A, 75B, 76-78 provide variousillustrations of different node-enabled packaging materials that may beused as part of a node package.

In an embodiment, exemplary packaging material may be used as at leastpart of a shipping container (e.g., box, enclosure, etc.) in a varietyof forms. For example, the packaging material may be used as a base,sides, and sealable lid from one or more sheets of packaging material tocreate and form the container itself, such as a corrugated fiberboardbox. In another example, the exemplary packaging material may be used aspackaging separator material where one or more sheets may be configuredin various orientations and with uniform or non-uniform surfaces toseparate distinct items being shipped together from each other withinthe same package container. In still another example, the exemplarypackaging material may be used as cushioning material for an itemrelative to an interior base, side, or lid surface so that the itembeing shipped is more protected from impacts to the package container.In some embodiments, such packaging material may form the containeralone. In other embodiments, the packaging material may act as separatormaterial as well as cushioning material. And in still other embodiments,the packing material may operate as all three—the material making up thecontainer, the separator materials, and the cushioning material.

As discussed in more detail below, a node (such as an ID node or masternode) may be generally assembled as part of such packaging material inan embodiment. For example, the node may be placed within a recessedpart of the packaging material and held in place, it may be adhered toan interior surface of the packaging material, it may be integrated aspart of the packaging material, and may be embedded within the packagingmaterial where some or none of the node is exposed outside the packagingmaterial. Such node-enabled packaging material may then be madeavailable to a shipping customer as part of a consumer product (e.g., anode-enabled shipping box) that can be purchased for later use whenshipping an item.

Those skilled in the art will appreciate that the described embodimentsof node-enabled packaging and methods of using them effect animprovement in how an item may be shipped while providing easier accessto relevant information about the shipped item. Such an enhanced abilityto ship an item in a container made with node-enabled packaging materialimproves technical fields such as logistics, shipping management,inventory management, and the like. In other words, the exemplaryembodiments described herein with interrelated operations between a nodedevice embedded within packaging materials and other elements of awireless node network (e.g., a master node, a server, and/or a useraccess device operated by a shipping customer) provide a type ofspecially-adapted node-enabled packaging material for use in shipping anitem that enhances and improves operations in technical fields such aslogistics, shipping management, retail inventory management, and thelike.

FIG. 75A is a diagram illustrating an exemplary container usingnode-enabled packaging material as part of an exemplary wireless nodenetwork in accordance with an embodiment of the invention. Referring nowto FIG. 75A, exemplary container 7500 (e.g., a box or other package) isillustrated that contains an item to be shipped 7510. Exemplary ID node7505 is shown as part of packaging material (such as fiberboardmaterial) that makes up container 7500. As shown, ID node 7505 isattached with adhesive to an interior surface of container 7500. Thoseskilled in the art will appreciate that while the container 7500 isshown as a cardboard box, in other embodiments, the container may havepackaging material made from other materials, such as metal, plastic,closed-cell extruded polystyrene foam (such as the Styrofoam™ brand fromThe Dow Chemical Company), or other materials used to make containerswithin which an item may be shipped.

In other embodiments, ID node 7505 may be embedded within the packagingmaterial. For example, FIG. 75B is a diagram illustrating anotherexemplary container using node-enabled packaging material as part of anexemplary wireless node network in accordance with an embodiment of theinvention. Referring now to FIG. 75B, exemplary container 7530 is shownbeing made with packaging material (such as corrugated fiberboard,plastic, closed cell foam, a foam injected interior with roto-moldedside walls, a combination of different materials, etc.) where the IDnode 7540 is embedded within a sheet of the packaging material making upat least part of container 7530. Those skilled in the art willappreciate that a general embodiment of such a “sheet” may have planarsurfaces; however, other embodiments may have an exemplary sheet ofpackaging material in the form of a block or other shape (withoutrequiring planar surfaces) as long as packaging material is disposedbetween the surfaces.

FIG. 76 is a diagram illustrating a view of an exemplary container sheetusing node-enabled packaging material as part of an exemplary wirelessnode network in accordance with an embodiment of the invention.Referring now to FIG. 76, exemplary container sheet 7600 is illustratedas a single sheet of packaging material, such as fiberboard material.Sheet 7600 includes fold lines that separate sheet 7600 into distinctparts of a container formed from the sheet 7600. In the illustratedembodiment, a base panel 7605 appears central to the sheet 7600 and hasextension panels 7610 a, 7610 b, 7615 a, 7615 b that become the sidewalls and lid sections when assembled (as shown in perspective in FIG.77).

In this exemplary embodiment, one of the panels 7615 b includes arecessed node region 7620 where a node may be mounted. As shown in FIG.76, the recessed node region 7620 in sheet 7600 may initially be openand accessible for mounting a master node or ID node. Mounting, forexample, may be accomplished by adhesive or other restraints (tape,etc.). In one example, the node may be placed in the recessed region7620 and an adhesive label may be place over the node while alsooverlapping onto the extension panel 7615 b. Thus, the adhesive labelmay hold the node in place within region 7620 but may allow forreplacement of the node so that the node and/or the container formedfrom sheet 7600 may be reused in other scenarios with other components.

Additionally, in the illustrated exemplary embodiment, panel 7615 bincludes an opening. The opening allows a status light (not shown) fromthe node to be aligned and mounted. In one embodiment, the status lightmay be integral to the node itself and, thus, the opening may appearwithin recessed region 7620. In another embodiment, the status light maybe electrically coupled (e.g., via wire or traces internal to panel 7615b) to the node within the recessed region 7620 with the light beingphysically separate from the node.

In another embodiment, sheet 7600 has no opening for the light to beshown through the sheet, but may yet still provide light from the statuslight visible from outside the assembled container from sheet 7600. Forexample, at least a portion of the packaging material making up therecessed portion 7620 may be clear or translucent to allow for light (orat least a glow of light) to be apparent from outside the assembledcontainer from sheet 7600. In another example, the status light may bedisposed on the node placed within recessed region 7620, and facing theexterior of the container when assembled from sheet 7600. A small partof the packaging material making up extension panel 7615 b may have asee through membrane (e.g., clear tape or the like) right where it wouldalign with the status light.

As previously explained with respect to exemplary ID and master nodes,an exemplary status light used with such nodes may also indicate ashipment state (such as a status of the shipped item, or a status alongthe transit journey for the shipped item in the container of packagingmaterial). The status light may also, in another embodiment, indicate asensed error or exceeded threshold by the node.

FIG. 77 is a diagram illustrating a perspective view of an exemplaryassembled container using node-enabled packaging material as part of anexemplary wireless node network in accordance with an embodiment of theinvention. Referring now to FIG. 77, a container may be assembled or,more generally, formed from the sheet 7600 and used to package an item(such as item 7535 or 7510) to be shipped. As the extension panels arefolded along the fold lines shown in FIG. 76, the container takes form.Once the node and status light (if used in opening 7625) are integratedas part of the packaging material that forms at least a part of thecontainer, the item to be shipped may be placed within the container andthe container may be sealed. Typically, sealing is done after activatingthe node, but depending on how activation may be accomplished with thenode integrated as part of the container, activation may occur after thecontainer is sealed as well.

In some embodiments, the item to be shipped may need further support andcare to make sure it arrives undamaged. To facilitate such undamagedtransit for an item to be shipped, separator packaging material and/orcushioning packaging material are often used. In some embodiments, thepackaging material making up such separator packaging material and/orcushioning packaging material may also include a node integrated in oneor more of these packaging materials and operative to be a node in awireless node network. FIG. 78 is a diagram illustrating a perspectiveview of exemplary node-enabled packaging material implemented withexemplary packaging separator sheet material and exemplary cushioningmaterial in accordance with an embodiment of the invention. Referringnow to FIG. 78, container 7500 is shown again but this time showing aninterior of the container 7500. Specifically, the interior of container7500 is shown having separator packaging material 7800 and cushioningpackaging materials 7805 a, 7805 b disposed within it. Exemplaryseparator packaging material 7800 is shown deployed essentiallybisecting the interior region of the container 7500, and providing aprotective segmentation of the interior so that more than one item maybe shipped in container 7500 without damage. And in an embodiment,separator packaging material 7800 may have a node 7820 integrated aspart of the material (e.g., attached to, embedded within, etc.).Likewise, exemplary cushioning packaging material 7805 a, 7805 b isshown deployed along the base of container 7500 provides a protectivecushioning barrier for an item within container 7500 and may have a node7810 integrated as part of the material. Such node-enabled packagingmaterial may be reused in a variety of shipping scenarios, may be soldin sheets that can be custom cut and fit to the particular shippingcustomer's intended container, separator, or cushioning requirements(while retaining the integrated node).

Another embodiment includes a node-enabled apparatus for packaging anitem to be shipped. The apparatus generally comprises packaging materialand an ID node integrated as part of the packaging material. Thepackaging material is used as part of a container that packages the itemto be shipped. For example, as discussed above regarding FIGS. 75A, 75B,and 76-78, such packaging material may be part of the panels making upthe structure of the container, separator sheets deployed as part of thecontainer to keep items separated from each other within the container,or cushioning material used to protect the packed items from the base,walls, and lid of the container. Thus, in one embodiment the packagingmaterial may comprise one from a group consisting of a fiberboardcontainer sheet, a packaging separator sheet, and cushioning materialsheet.

The ID node integrated as part of the packaging material of thenode-enabled apparatus is operative to communicate directly with amaster node (e.g., exemplary master node 110 a shown in FIG. 4 or masternode 7515 illustrated in FIGS. 75A-B) in a wireless node network but isunable to directly communicate with a server (e.g., server 100 shown inFIGS. 5 and 75A-B) in the wireless node network. In more detail, the IDnode further comprises a processing unit and a communication interfacecoupled to the processing unit. The communication interface provides acommunication path (e.g., a short range communication path, such as aBluetooth® formatted communication path) to the master node. Thecommunication interface can also receive a message broadcast from themaster node and provide the message to the processing unit.

The ID node in the apparatus further comprises a volatile memory coupledto the processing unit and a memory storage coupled to the processingunit. Examples of such memory are shown in FIG. 3 as memory storage 315and volatile memory 320. The memory storage maintains code for executionby the processing unit and shipping information related to the containerand the ID node integrated as part of the packaging material. Duringoperation of the ID node, the code (e.g., node management and controlcode 325) may be loaded from memory storage and run in volatile memory.

The ID node in the apparatus also comprises a power source forenergizing the ID node. For example, such a power source may be battery355. In one embodiment, the power source within the ID node mayinitially be assembled to have a non-conductive strip that interruptsany possible current flow out of the power source and into the circuitryof the ID node as a way of best preserving the life of the power source.This embodiment allows the consuming shipping customer to purchase thenode-enabled apparatus for a future use when shipping an item, and allowthe customer to remove the non-conductive strip from between the powersource (e.g., a terminal of battery 355) and a power terminal for the IDnode that is normally coupled to the power source.

The processing unit of the ID node in the apparatus, when executing thecode, is operative to receive the shipping information from a first node(e.g., a master node) in the wireless node network, cause an advertisingsignal to be broadcast over the communication interface to the masternode, and share at least a part of the shipping information with themaster node. In more detail, sharing such information may beaccomplished when the server provides an authorization to activelyconnect and associate with the master node (which may be preauthorizedor requested from the server when the master node detects theadvertising signal).

In a further embodiment, the node-enabled apparatus may also include astatus light indicative of an activated state of the ID node. Forexample, an exemplary status light may be implemented with a low powerLED light source coupled to circuitry on ID node that interfaces withsuch circuitry and can be driven by the processing unit. In oneembodiment, the processing unit may be further operative to cause thestatus light to blink in a designated pattern upon receiving theshipping information. This may allow the shipping customer a way toconfirm that the node-enabled apparatus is operating and ready to besealed within the container. For example, upon receipt of the shippinginformation, the processing unit may send control signals to theinterface circuitry coupled to the LED status light and the controlsignals may cause the light to blink on and off a predesignated numberof times to visually reflect receipt of the shipping information. Otherembodiments may have the processing unit exercising the light in otherpatterns to indicate different types of status conditions and provideadditional feedback to the shipping customer or package handlingpersonnel or light sensing machines that may process or sort the packagecontainer.

In another embodiment, the status light may be disposed within thepackaging material but viewable from outside the container. In oneexample, the status light may be disposed within the packaging materialwithout an opening, but be close enough to the exterior so that lightmay “glow” appear viewable (or partially viewable) from outside thecontainer. The status light may be disposed in a translucent part of thepackaging material advantageously located so it may be seen or easilyscanned.

In another example, as discussed above with respect to FIG. 76, anexemplary ID node may be disposed within recessed region 7620 and have astatus light viewable through opening 7625 or, if the light is part ofthe body of the ID node, a status light viewable through an opening (notshown) in recessed region 7620.

In still another embodiment, the packaging material may include anopening and the status light may be disposed in a configuration withinthe packaging material where the status light aligns with the opening.As shown in FIG. 76, for example, an exemplary opening 7625 may bealigned with a separately mounted status light coupled to the ID node.

The ID node integrated as part of the packaging material in theapparatus may further comprise a switch coupled to the power source forallowing the power source to energize the ID node. For example, as shownin FIG. 3, ID node 120 a includes a magnetic switch that is magneticallyactivated when the switch detects a set of magnetic field changes. Inmore detail, the detected set of magnetic field changes detected by theswitch may further comprise a series of magnetic field changes over aperiod of time that defines an activation pattern. Such a pattern may beactuated by physical movement of a magnetic field source (e.g., amagnet) near the node in such a timed manner as to present the series ofmagnetic field changes over time.

In another embodiment, the ID node integrated as part of the packagingmaterial in the apparatus may further comprise a logical input to theprocessing unit that allows the power source to energize the ID node.

In one embodiment, the packaging material may include at least a sheetof packaging material, such that the ID node integrated as part of thepackaging material may be embedded within the sheet of packagingmaterial. For example, the ID node 7540 shown in FIG. 75B is embeddedwithin a sheet of packaging material making up a panel base of thecontainer 7530.

Typical embodiments of such a node-enabled apparatus may include acontainer advantageously having an integrated or embedded ID node withinthe packaging material making up the container. How such node-enabledpackaging material may be used is also the subject of variousembodiments. FIG. 79 is a flow diagram illustrating an exemplary methodusing node-enabled packaging material as part of a container for an itemto be shipped in accordance with an embodiment of the invention.

Referring now to FIG. 79, method 7900 begins at step 7905 by forming atleast a part of the container with the packaging material. In oneembodiment, the packaging material may comprise one from a groupconsisting of a fiberboard container sheet, a packaging separator sheet,and cushioning material sheet.

At step 7910, method 7900 continues by activating an ID node integratedas part of the packaging material. The ID node is operative tocommunicate directly with a master node in a wireless node network overbut is unable to directly communicate with a server in the wireless nodenetwork. For example, as shown in FIG. 75A, ID node 7505 can communicatedirectly with master node 7515 (associated with and part of node-enabledlogistics receptacle or node-enabled drop box 7520) but is unable todirectly communicate with server 100. Instead, ID node 7505 relies onthe hierarchy of master node 7515, which is able to communicate directlywith server 100 through network 105.

In one embodiment of method 7900, activating the node integrated as partof the packaging material may be accomplished in various ways. Forexample, the node may have sensors built into the packaging materialsuch that as the material forms a container and a lid part of thecontainer is closed, the sensors detect such a closing and responds byactivating the node. In another example, two surfaces of the packagingmaterials may have built-in sensors, which when pressed togetheractivate the node. And as explained above, another example may deploy amagnetic switch that, when changing states under the appropriatemagnetic stimulus, may activate the node.

Activating the node may cause the node to energize from a completelyunpowered condition. In another example, activating the node may causethe node to move from a lower energy consumption state (e.g., a standbymode) to a higher functioning state or fully functioning state. As such,prior to activation, a node may remain in an exemplary standby modewhere part of the node functions but does so while attempting tominimize the consumption of energy. For example, an exemplary node maykeep its communication interface(s) powered down (e.g., radio off) whenin standby, but power such circuitry on when activated so that the nodecan begin to communicate with other nodes or the server in the wirelessnode network.

In one embodiment, activating the ID node may further comprise causing apower source within the ID node (e.g., battery 355 of exemplary ID node120 a) to energize the ID node integrated as part of the packagingmaterial of the container and to turn on a status light of the ID node.

At step 7915, method 7900 continues by registering shipping informationwith the server via a user access device operated by a shippingcustomer, the shipping information being related to the container andthe ID node integrated as part of the packaging material of thecontainer. As explained with reference to FIG. 2, an exemplary useraccess device in various embodiments (such as device 200) may beimplemented with a desktop computer, laptop computer, tablet (such as anApple iPad® touchscreen tablet), a personal area network device (such asa Bluetooth® device), a smartphone (such as an Apple iPhone®), a smartwearable device (such as a Samsung Galaxy Gear™ smartwatch device, or aGoogle Glass™ wearable smart optics) or other such devices capable ofcommunicating over network 105 with server 100, over a wired or wirelesscommunication path to master node and ID nodes. And as shown in theexample illustrated in FIG. 75A, user access device 200 may be asmartphone operated by a shipping customer running an app (that mayimplement code 425 explained above) to allow direct access to server100. In one example, the customer may have purchased container 7500(which has integrated node 7505) at a shipping facility, a retailoutlet, or via an online order for such a node-enabled apparatus.

In a more detailed embodiment, registering may comprise entering adestination address for the container into the user access device as afirst part of the shipping information; entering a tracking number intothe user access device as a second part of the shipping information(where the tracking number is related to the container); entering a nodeidentification (e.g., a MAC address related to the ID node integrated aspart of the packaging material of the container) into the user accessdevice as a third part of the shipping information; and causing the useraccess device to transmit the shipping information to the server.

Additionally, registering may comprise entering container contentinformation that describes the item to be shipped in the container madefrom the packaging material. In one particular example, the containercontent information may further comprise customs information for acustoms declaration on the item in the container. Once generated andsupplied to the server, such container content information may beprogrammed into and stored within memory of the ID node integrated aspart of the packaging material.

At step 7920, method 7900 may continue by sealing the item within thecontainer having the ID node integrated as part of the packagingmaterial of the container. And at step 7925, method 7900 continues byplacing the container at a first hand-off point for shipping thecontainer.

In one embodiment, the placing step may further comprise providing thecontainer to a courier associated with the master node near the firsthand-off point. For instance, in the example illustrated in FIG. 75A,master node 7515 may be associated with a courier. As the courierreceives the container 7500 having the integrated ID node 7505, thecourier's master node 7515 associates with the ID node 7505 at thehand-off point (e.g., a mail room in an office building, a packagestorage room at a shipping facility, etc.).

However, in another embodiment, the placing step may further comprisedepositing the container in a node-enabled logistics receptacle servicedby a courier, where the node-enabled logistics receptacle is at thefirst hand-off point. Referring back to the example illustrated in FIG.75A, master node 7515 may be part of a node-enabled logistics receptacleor, more generally, a node-enabled logistics receptacle 7520 that canreceived package containers being shipped and hold them for one or morecouriers to service the unit and pick up relevant package containersbeing shipped.

Proactive Re-Route Notification Using a Node-Enabled LogisticsReceptacle

Other embodiments may have one or more nodes in a wireless node networkfacilitating proactive notification of a shipping customer as thecustomer attempts to ship a package. The shipping customer may haveinput and otherwise provided shipping information to a server for thepackage to be shipped, and then be traveling on their way to theshipping facility (e.g., such as a FedEx® Office Print & Ship Center orthe like) to drop off the package. Dropping off the package with thefacility, for example, may be where the package begins its anticipatedtransit from an origin location to a destination location.

One issue that may be encountered is when the shipping facility isunable to accept the package for some reason (e.g., the facility isclosed, particular equipment may be inoperable, scheduled pickup by acourier has already occurred, the facility cannot handle the type ofitem to be shipped, and the like). In general, an embodiment wherecertain network devices in a wireless node network are deployed mayprovide proactive notification to the shipping customer to re-route thecustomer away from the facility that is unable to accept the package,and towards an alternative shipping solution (e.g., another facility, anode-enabled logistics receptacle, etc.) so that the customer may stillhave the package shipped.

FIG. 80 is a diagram illustrating an exemplary user access device andpackage approaching an exemplary shipping facility where an exemplarysystem notifies a shipping customer about an alternative shippingsolution in accordance with an embodiment of the invention. Referringnow to FIG. 80, a shipping customer's smartphone 200 (a type of useraccess device) and the package 8005 are shown approaching an exemplaryshipping facility 8000. The facility 8000 has deployed within or aroundit a shipping facility master node 8110 a, similarly structured andprogrammed as set forth for exemplary master node 110 a in FIG. 4. Assuch, shipping facility master node 8110 a is operative to directlycommunicate with server 100 via network 105.

In an embodiment, the shipping customer's smartphone 200 may execute anapp (not shown) that in essential parts operates as code 325 or 425 tomake smartphone 200 operate as an exemplary ID node or exemplary masternode, respectively. As such, smartphone 200 may interact with server100, for example, to upload shipping information on the package 8005 tobe shipped. Likewise, smartphone 200 may exercise its Bluetooth®communication hardware and software (e.g., RF transceiver, programstacks, profiles, and the like) as a short-range communication interfaceto broadcast advertising signals 8015. As smartphone 200 approaches andgets close enough to shipping master node 8110 a, the master node 8110 amay begin to detect the signals 8015. Such signals 8015 may includeinformation in the status header that indicates smartphone 200 islooking to associate with another node. In one embodiment, onceassociated, the master node 8110 a may access server 100 to gatherfurther information (e.g., shipping information). In another embodiment,the master node 8110 a may receive such information directly from thesmartphone 200 after the active association between the smartphone 200and the shipping facility master node 8110.

At this point, the shipping customer may continue approaching theshipping facility 8000 and enter the facility 8000 to ship the package8005 if the facility 8000 is open and accepting packages for shipment.However, rather than simply arrive at facility 8000 and find out thenthat the package cannot be shipped from there as intended, an embodimentmay provide a proactive notification about an alternative shippingsolution to the smartphone 200 (as a type of user access device). Thoseskilled in the art will appreciate that smartphone 200 may beimplemented by others types of user access devices, such as a laptopcomputer, a tablet device, a personal area network device, or a smartwearable device. And in more detail, an embodiment may provide aproactive notification about an alternative shipping solution to theuser access device based upon the shipping information and a shippingstatus for the shipping facility.

In general, the shipping status relates to the ability or inability ofthe facility to accept and ship the package. Status information may beavailable on the shipping master node 8110 a and/or server 100 thatreflects such a shipping status. Likewise, such network devices may alsobe able to determine or identify an alternative shipping solution, suchas a nearby shipping facility open later that facility 8000 or a closeby node-enabled logistics receptacle. Other examples of an alternativeshipping solution may include logistics receptacles, such as aconventional non-node-enabled drop box, secure locker unit or other dropoff receptacle. As such, an exemplary proactive notification may providedirections to such an alternative shipping solution's location (thenearest 24-hour shipping facility, a close by node-enabled logisticsreceptacle, etc.).

In a more detailed embodiment, the proactive notification may be abeginning message of a two-way interactive dialog between the user ofthe smartphone 200 looking to find a suitable alternative shippingsolution and the master node or server providing other alternatives,relevant information about each alternative (e.g., distance from theuser's current location, hours of operation, types of courier serviceoffered, different types of shipping service offered, a schedule offuture pickup times). Additionally, the user of the smartphone 200 maybe provided, as part of such a two-way dialog started with the proactivenotification, an offer for premium or prioritized pickup to be schedulefor a selected node-enabled logistics receptacle.

For example, if the shipping customer using smartphone 200 is unable tohave facility 8000 ship the package 8005, the proactive notificationsent to smartphone 200 may include directions 8010 to a close by nodeenabled logistics receptacle 8110 b. Furthermore, the shipping customerusing smartphone 200 may be presented with options for other alternativeshipping solutions (e.g., other locations with other logisticsreceptacles or shipping facilities). Additionally, in an embodiment, theshipping customer using smartphone 200 may elect to go to node-enabledlogistics receptacle 8110 b and pay to have pickup prioritized at thatparticular unit. For example, such a payment may cause the receptacle8110 b to quickly report the pending package in its custody to server100 for a quicker pickup than normally provided with standard shippingservices. As such, payment may be made by the shipping customer usingsmartphone 200 (e.g., using wireless payment options with nodeassociations as discussed in more detail herein), and scheduleinformation for courier pick-up of packages within node-enabledlogistics receptacle 8110 b may be prioritized.

FIG. 81 is a flow diagram illustrating an exemplary method forproactively notifying a shipping customer using a wireless node networkabout an alternative shipping solution when shipping a package inaccordance with an embodiment of the invention. Method 8100 begins atstep 8105 by detecting a signal broadcast by a user access devicerelated to a shipping customer as the device approaches a master noderelated to a shipping facility, where the shipping customer isapproaching the shipping facility with the package to be shipped. Inanother embodiment of method 8100, the user access device may detect asignal broadcast by the master node related to the shipping facility asa prelude to associating in step 8110.

Here, the user access device (e.g., smartphone 200 as shown andexplained in FIG. 80) is operating as a node in the network. In a moredetailed embodiment, the user access device may be operating as an IDnode in the network, and as such may be operative to directlycommunicate with the shipping facility master node but unable todirectly communicate with the server in the network. However, in anotherembodiment, the user access device may be operating as another masternode in the network, such that the device can directly communicate withthe shipping facility master node and directly communicate with theserver in the network. Indeed, an example smartphone 200 may have an appthat allows it to operate as a master node in some instances and as anID node in other instances.

At step 8110, method 8100 continues by associating the user accessdevice with the shipping facility master node. This may be accomplishedwith establishing a passive or active connection between the device andthe master node. The active connection may allow for secured sharing ofinformation, such as shipping information in one embodiment.

At step 8115, method 8100 continues with an embodiment where, ratherthan receive the shipping information from the user access device, theshipping facility master node receives the shipping information relatedto the package to be shipped from the server. In one example, this maybe done after the shipping facility master node associates with the useraccess device. However, in another example, the shipping facility masternode may have received the shipping information prior to associatingwith the user access device. Thus, the server may have pre-staged theshipping information with the shipping master node in anticipation ofthe shipping customer bringing the package to the facility (such asfacility 8000) for shipping.

Additionally, in another embodiment the shipping facility master nodemay be pre-staged with service information. For example, such serviceinformation may outline or otherwise define classes of acceptableshipping services provided by the shipping facility. In more detail,such service information may also include alternative shipping solutioninformation to be provided to the user access device.

At step 8120, method 8100 continues by providing a proactivenotification about an alternative shipping solution to the user accessdevice based upon the shipping information and a shipping status for theshipping facility. For example, exemplary shipping information mayidentify a particular shipping service desired, and the shipping statusinformation for the facility may indicated that desired service is notoffered or is temporarily offline (e.g., due to equipment maintenanceissues, inability to accept more due to being a maximum capacity, or thelike).

In one embodiment, the step of providing the proactive notification tothe user access device may be performed by one of the shipping facilitymaster node and the server. For example, an embodiment may have moredetails on what other alternative shipping solutions are available onthe backend server 100, rather than maintaining such information onshipping facility master node 8110 a. However, in another embodiment,shipping facility master node 8110 a may be a robust computing platformand its memory storage may contain such information depending on theimplementation and so it can offload the server 100 from needing torespond with such a notification or, in more detailed embodiments,interactive messaging between the device 200 and the system (e.g.,master node 8110 a or server 100).

In several other embodiments, the shipping status for the shippingfacility may be implemented in various ways. In a general embodiment,the shipping status for the shipping facility may comprise whether theshipping facility is unable to accept any package for shipment. In amore detailed example, the shipping status may comprise whether theshipping facility is not currently open for business. The shippingcustomer may be attempting to drop off the package to be shipped afternormal business hours for the facility, or at least when a shippingdepartment portion of the shipping facility is not currently open forbusiness. In yet another detailed example, the shipping status maycomprise whether the shipping facility is unable to accept one or morecategories of shipments related to the package (such as dangerous goods,or types of pickup entities that may not service the shipping facility).

In another example, the shipping status for the shipping facility maycomprise whether the shipping facility is no longer scheduled for apickup event by a desired shipping courier identified in the shippinginformation. For instance, the shipping customer may be approaching theshipping facility after the last pickup by a courier for that day. Inmore detail, when the shipping information identifies a desired shippingcourier, that particular shipping courier may not be scheduled to cometo the shipping facility that day while other couriers may still bescheduled to pick-up packages identified to be handed off to them forfurther shipping through their respective shipping entity's logisticsnetwork.

In still another example, the shipping status for the shipping facilitymay comprise whether the shipping facility is unable to accept a packagefor shipment by a desired shipping service identified in the shippinginformation. For instance, a single shipping entity may provide a fastershipping service (e.g., overnight) and a more standard shipping servicethat costs less than the faster service. The shipping status, in such asituation, may indicate that while it can accept packages for thestandard shipping server, it cannot ship any more packages with thefaster shipping service that day given the logistics resources alreadydeployed by the shipping entity.

In another embodiment, the proactive notification about the alternativeshipping solution may include information about an alternative shippingfacility that is able to accept the package for shipment as thealternative shipping solution. In the example shown in FIG. 80,smartphone 200 may receive an exemplary proactive notification as thedevice approaches facility 8000 where the notification includes a nameof another shipping facility, location, hours of service, and types ofservice provided by one or more shipping entities.

In still another embodiment, the proactive notification about thealternative shipping solution may comprise information about anode-enabled logistics receptacle that is able to accept the package forshipment as the alternative shipping solution. In more detail, theinformation about the node-enabled logistics receptacle that is able toaccept the package for shipment may include directions to thenode-enabled logistics receptacle. For instance, such a notification mayinclude information that identifies node-enabled logistics receptacle8110 b, which may be available to intelligently accept, track, report,and manage the location and status of package 8005 immediately uponreceipt. And that information may include directions 8010 to be shown tothe shipping customer via a user interface on device 200.

In an even more detailed embodiment, the step of providing the proactivenotification about the alternative shipping solution may comprisedetermining, by the server, a location of the user access device;determining if the shipping information and the shipping status for theshipping facility indicate the shipping facility is unable to accept thepackage for shipment; identifying a node-enabled logistics receptaclenear the shipping facility (e.g., unit 8110 b near facility 8000) as thealternative shipping solution; and transmitting the proactivenotification to the user access device, where the proactive notificationprovides directions to the identified node-enabled logistics receptacle.

And in a further embodiment of method 8100, the identifying stepexplained above may further comprise determining which one of aplurality of node-enabled logistics receptacles is a closest unit to theuser access device with a capacity to accept the package for shipment;and identifying the determined one of the node-enabled logisticsreceptacles to be the alternative shipping solution comprising thenode-enabled logistics receptacle near the shipping facility. Here,there may be a large number of potential alternative shipping solutionsand the master node or server may determine which is closest.Alternatively, a set of choices for close units within a prompted rangemay be provided where the notification is a beginning message in a moreinteractive exchange to proactively help the shipping customer ship thepackage in an efficient manner.

Those skilled in the art will appreciate that method 8100 as disclosedand explained above in various embodiments may be implemented on amaster node (such as exemplary master node 110 a as illustrated in FIG.4, and shipping facility master node 8110 a in FIG. 80), running one ormore parts of a control and management code (such as code 425) toimplement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium (such as memorystorage 415 in an exemplary mobile master node). Thus, when executingsuch code, a processing unit of the master node (such as unit 400) maybe operative to perform operations or steps from the exemplary methodsdisclosed above, including method 8100 and variations of that method.

Self-Assessing a Location for Node-Enabled Logistics Receptacle

As described above, an embodiment may implement a node as part of orconnected/attached to a logistics receptacle, such as a shipping dropbox or secure locker unit. FIGS. 82A and 82B illustrate an exemplarynode-enabled logistics receptacle. Referring now to FIG. 82A, exemplarynode-enabled logistics receptacle 8200 is illustrated in perspectivehaving a deposit entrance 8205 and a payload access door 8210. Thenode-enabled logistics receptacle 8200 is typically placed in anaccessible location where shipping customers may have access toreceptacle 8200. In operation, a shipping customer may articulate andopen a door at the deposit entrance 8205 so that the receptacle 8200 mayreceive a package. Once the package is placed within the receptacle8200, and the shipping customer closes the door at the deposit entrance8205, the package is then maintained within the receptacle. In otherwords, the exemplary node-enabled logistics receptacle 8200 can receiveand temporarily maintain custody of a package being shipped, and it doesso with an entrance opening 8205 through which the package is receivedby the receptacle and a temporary storage area within the receptaclewhere the package is temporarily and securely maintained until anauthorized pickup. Typically, a shipping entity's courier personnel mayarrive and pickup any deposited packages using payload access door 8210and security lock 8215.

FIG. 82B is a diagram illustrating a side and internal view into theexemplary node-enabled logistics receptacle 8200 of FIG. 82A inaccordance with an embodiment of the invention. Referring now to FIG.82B, more details of the exemplary node-enabled logistics receptacle8200 are shown. For example, the node-enabled logistics receptacle 8200is shown having a node 8220 as part of the receptacle structure. In oneembodiment, node 8220 may be implemented as an ID node; in otherembodiments, node 8220 may be implemented as a more complex master node.Node 8220 may be integrated or embedded within the node-enabledlogistics receptacle 8200. Other embodiments may simply have the node8220 attached to some part of the node-enabled logistics receptacle8200, such as to an accessible portion of the interior regions 8225,8230 of node-enabled logistics receptacle 8200. With such a removableimplementation of node 8220, various service operations related to thenode 8220 may be easier to accomplish (e.g., replacement of the node,replacement of the node's battery, replacement of the node's sensor(s),adding more memory to the memory onboard the node, and the like).

In operation, a shipping customer may insert a package 8235 through theopening 8205 by opening a door for the opening. The package, such aspackage 8235, may then be placed within a first interior region 8225. Insome embodiments, those skilled in the art will appreciate that thenode-enabled logistics receptacle 8200 may include further structure toaccept the package 8235 in region 8225 while preventing removal of anypackages or items from within the node-enabled logistics receptacle8200.

Once within region 8225, the package 8235 then drops into or otherwisemoves into a second interior region 8230. Region 8230 is typically usedas a temporary storage area within the receptacle 8200 where the package8235 can be temporarily and securely maintained until an authorizedpickup. In one example, a shipping entity's courier personnel may arriveand pickup any deposited packages using payload access door 8210 andsecurity lock 8215.

And as discussed in more detail with respect to other embodimentsdisclosed herein (e.g., embodiments illustrated in FIGS. 89A and 89B),an exemplary node-enabled logistics receptacle may be able to sense whena package having a node (generally referred to as a “node package”) isapproaching, and in some embodiments can detect when a node package ornon-node package has been deposited within the receptacle.

One issue that may be faced related to deploying a node-enabledlogistics receptacle, such as receptacle 8200, at a particular locationis assessing whether the location is a suitable location for thenode-enabled logistics receptacle. If the location does not have asuitable amount of potential shipping customers that may use thereceptacle, the costs of deploying such a node-enabled logisticsreceptacle may not be justified. Additionally, business and consumeractivity surrounding a particular location may change over time. Suchbusiness and consumer activity may have initially justified placement ofthe node-enabled logistics receptacle at the particular location, but anembodiment may allow for on-going and future re-assessments of whetherkeeping the node-enabled logistics receptacle at that location isjustified.

In one embodiment, a node-enabled logistics receptacle, such asexemplary node-enabled logistics receptacle 8200, is able to self-assessits current location. For example, FIG. 83 is a diagram illustrating anexemplary node-enabled logistics receptacle that is operative to assessthe suitability of a current location of the exemplary node-enabledlogistics receptacle in accordance with an embodiment of the invention.Referring now to FIG. 83, an embodiment is shown where node-enabledlogistics receptacle 8200 is operative to communicate directly with aserver 100 over network 105. Thus, the node 8220 within receptacle 8200in this embodiment is a master node. However, in another embodiment,node 8220 within receptacle 8200 may be implemented with an ID node, andnode-enabled logistics receptacle 8200 may be operative to directlycommunicate with a master node (not shown) in the wireless node network,which can then directly communicate with server 100.

The logistics receptacle 8200, as explained with reference to FIGS. 82Aand 82B, can receive and temporarily maintain a package being shipped.And as shown in FIG. 82B, the receptacle has an entrance opening throughwhich the package is received and a temporary storage area (such asregion 8230) where the package is temporarily and securely maintaineduntil an authorized pickup.

The node-enabled logistics receptacle also comprises a node assembledwith the receptacle such that there is a general relationship betweenthe node and the receptacle. The node, for example, may be assembledwith the receptacle by being attached to, integrated as part of, orfully or partially embedded within the structure of the receptacle. Inone embodiment, the node may be implemented with ID node 120 aillustrated in FIG. 3; likewise, in another embodiment, the node may beimplemented with master node 110 a illustrated in FIG. 4.

In more detail, the node assembled with the logistics receptacle furthercomprises a node processing unit, a node memory storage, and at leastone communication interface. The node memory storage is coupled to thenode processing unit and maintains code for execution by the nodeprocessing unit and a user criteria level related to wirelesscommunication signal activity near the embedded node assembled with thereceptacle.

The communication interface (or each communication interface when thereare multiple interfaces) is/are coupled to the node processing unit. Thecommunication interface is generally operative to detect a signalbroadcast from a wireless user access device (such as a smartphone) andcommunicate with another network device in the wireless node network(such as an ID node, a master node, or the server).

The node processing unit, when executing the code maintained on the nodememory storage, is operative to perform various functions thatcollectively allow the node-enabled logistics receptacle to assess acurrent location for a node-enabled logistics receptacle. In moredetail, the node processing unit is operative to detect a level ofwireless communication signal activity on the at least one communicationinterface. In the example illustrated in FIG. 83, the node-enabledlogistics receptacle 8200 is shown to be detecting wirelesscommunication signal activity on its communication interface (e.g.,medium/long range communication interface 485 when the node is a masternode like node 110 a shown in FIG. 4). As shown in FIG. 83, receptacle8200 is operative to detect activity from four different wirelessdevices, such as smartphone 8305, laptop computer 8310, tablet device8315, and personal area network device 8320.

The node processing unit is also operative to record the detected levelof wireless communication signal activity over a predetermined period oftime in the node memory storage. Thus, in the example shown in FIG. 83,the node processing unit within node 8220 of receptacle 8200 may recordthe detected level of wireless communication signal activity over aweek, for example, in onboard memory within the node 8220. The activitylevel may, for example, be recorded as a number of signals detected, thesignal strength of the signals detected (e.g., based on a receivedsignal strength indication or RSSI), or a combination thereof. Otherembodiments may record the activity level as signals detected duringspecific time intervals (e.g., during convention business hours, beforebusiness hours, during a lunch time interval, after business hours,during rush hour, during certain days of the week, during holidayperiods, and the like).

The node processing unit is also operative to compare the recorded levelof wireless communication signal activity to the user criteria level forthe node-enabled logistics receptacle maintained in the node memorystorage. Based upon the comparison of the recorded level and the usercriteria level, the node processing unit is operative to assess thecurrent location for the node-enabled logistics receptacle. If theprocessing unit assesses that the current location does not meet theuser criteria level, the unit may transmit an alert message to anothernetwork device in the network.

In one embodiment, the alert message may provide the recorded level ofwireless communication signal activity over the predetermined period oftime to at least one of a master node in the network or a server in thenetwork. For example, in the FIG. 83 example, node-enabled logisticsreceptacle 8200 is shown as operative to communicate directly with theserver 100 via network 105 (i.e., not through an intermediary wirelessnode in the wireless node network before getting to server 100).However, another embodiment may have node-enabled logistics receptacle8200 communicating the alert message to another node (e.g., a masternode not shown in FIG. 83), which may forward the alert message orotherwise notify the server 100 about the alert message.

In another embodiment, the node processing unit is further operative todetect the level of wireless communication signal activity by beingoperative to detect a number of signals broadcast by at least onewireless user access device. Thus, the number of signals broadcast byone or more than one wireless user access devices (e.g., one or morenetwork devices from a group comprising a laptop computer, a tabletdevice, a personal area network device, a smartphone device, and a smartwearable device) may be the detected level of wireless communicationsignal activity. The wireless user access device(s) have users that mayinteract with one or more network devices of a wireless node network,such as the node in the node-enabled logistics receptacle.

In a more detailed embodiment, the user criteria level may be athreshold number of signals broadcast by the at least one wireless useraccess device and detected by the node-enabled logistics receptacle. Inother words, the node-enabled logistics receptacle may listen for andrecord indications of a level of potential customers that may use thereceptacle. As such, this embodiment may consider a threshold number ofdetects signals from wireless user access devices to be a suitable usercriteria level.

In still another embodiment, the detected level wireless communicationsignal activity over the predetermined period of time further may bebased upon a number of detected signals broadcast by at least onewireless user access device and a strength of each of the detectedsignals broadcast by the at least one wireless user access device, andfurther still, the user criteria level may be a threshold number ofdetected signals broadcast by the at least one wireless user accessdevice. In an even more detailed embodiment, the user criteria level maybe a threshold number of detected signals broadcast by the at least onewireless user access device having at least a threshold strength. And inyet a further detailed embodiment, the user criteria level may be athreshold number of detected signals broadcast by the at least onewireless user access device having a minimum relative received signalstrength (such as an RSSI that effectively focuses the relevant group ofdetected signals to those within a reasonable range from thenode-enabled logistics receptacle.

FIG. 84 is a flow diagram illustrating an exemplary method for assessinga current location for a node-enabled logistics receptacle in accordancewith an embodiment of the invention. Referring now to FIG. 84, method8400 begins at step 8405 by detecting a level of wireless communicationsignal activity on a communication interface on the node-enabledlogistics receptacle, where the node-enabled logistics receptacle canreceive and temporarily maintain a package being shipped. For example,as shown in FIGS. 82A and 82B, node-enabled logistics receptacle 8200can receive and temporarily maintain package 8235 in region 8230 as itis being shipped and can detect, as shown in FIG. 83, a level ofwireless communication signal activity from network devices (such aswireless user access devices—e.g., smartphone 8305, laptop computer8310, tablet device 8315, and personal network device 8320).

In a further embodiment of method 8400, the detecting step may comprisedetecting the level of wireless communication signal activity asdetecting a number of signals broadcast by one or more wireless useraccess devices that allow a user to interact with one or more networkdevices of a wireless node network. Examples of a wireless user accessdevice may be a network device, such as a laptop computer, a tabletdevice, a personal area network device, a smartphone device, and a smartwearable device. Additionally, method 8400 may have the user criterialevel being a threshold number of signals broadcast by the at least onewireless user access device and detected by the node-enabled logisticsreceptacle.

In a more detailed embodiment of method 8400, the detected levelwireless communication signal activity over a predetermined period oftime may be based upon a number of detected signals broadcast by atleast one wireless user access device and a strength of each of thedetected signals broadcast by the at least one wireless user accessdevice (e.g., an RSSI based strength of the detected signals).Additionally, in such an embodiment, the user criteria level may furtherbe implemented in a variety of useful ways, such as with a thresholdnumber of detected signals broadcast by the at least one wireless useraccess device; with a threshold number of detected signals broadcast bythe at least one wireless user access device having at least a thresholdstrength; and with a threshold number of detected signals broadcast bythe at least one wireless user access device having a minimum relativereceived signal strength.

At step 8410, method 8400 continues by recording the detected level ofwireless communication signal activity over a predetermined period oftime in a memory disposed in the node-enabled logistics receptacle. Atstep 8415, method 8400 continues by comparing, by the node-enabledlogistics receptacle, the recorded level of wireless communicationsignal activity over the predetermined period of time to a user criterialevel for the node-enabled logistics receptacle. And at step 8420,method 8400 concludes by assessing the current location for thenode-enabled logistics receptacle based upon the comparison of therecorded level and the user criteria level.

In a further embodiment, method 8400 may also include transmitting analert message to another network device in the network when thenode-enabled logistics receptacle assesses the current location does notmeet the user criteria level. Additionally, the alert message mayprovide the recorded level of wireless communication signal activityover the predetermined period of time to at least one of a master nodein the network or a server in the network.

Those skilled in the art will appreciate that method 8400 as disclosedand explained above in various embodiments may be implemented onnode-enabled logistics receptacle having an ID node (such as exemplaryID node 120 a as illustrated in FIG. 3) or a master node (such asexemplary master node 110 a as illustrated in FIG. 4), running one ormore parts of a control and management code (such as code 325 for an IDnode based node-enabled logistics receptacle or code 425 for a masternode based node-enabled logistics receptacle) to implement any of theabove described functionality. Such code may be stored on anon-transitory computer-readable medium (such as memory storage 315 or415 in the respective exemplary nodes). Thus, when executing such code,a processing unit of the node (such as unit 300 or unit 400) may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 8400 and variations of that method.

Proactive Status Reporting from a Node-Enabled Logistics Receptacle

Servicing of a conventional logistics receptacle (e.g., a shippingdrop-box or secure locker unit) may be performed without proactivereporting from the receptacle itself. However, in the embodimentsdescribed below, an exemplary node-enabled logistics receptacle mayproactively facilitate more efficient and effective pick up of packagesbeing shipped and management of logistics receptacle resources thatallow a shipping customer to drop off a package for shipment.

FIGS. 82A and 82B and the accompanying description above provide a basicdescription of an exemplary node-enabled logistics receptacle.Additionally, FIG. 85A is a diagram illustrating an exemplarynode-enabled logistics receptacle with a master node assembled withinthe logistics receptacle and ready to receive a package in accordancewith an embodiment of the invention. Referring now to FIG. 85A,node-enabled logistics receptacle 8500 is illustrated having a masternode 8505 assembled within it (similar to node 8220 within receptacle8200 shown in FIG. 82B and exemplary master node 110 a shown in FIG. 4).In FIG. 85A, a package 8235 to be shipped is outside node-enabledlogistics receptacle 8500 prior to depositing the package 8235 into thenode-enabled logistics receptacle 8500. Once deposited withinnode-enabled logistics receptacle 8500, FIG. 85B illustrates the package8235 within the node-enabled logistics receptacle 8500 in accordancewith an embodiment of the invention.

As shown in FIGS. 85A and 85B, master node 8505 is operative tocommunicate within the wireless node network with various networkdevices—e.g., with other nodes (such as ID nodes and master nodes) aswell as communicate directly with server 100. Thus, the exemplarynode-enabled logistics receptacle 8500 is able to provide informationrelated to its contents through master node 8505 to server 100.

Similar to the node-enabled logistics receptacle 8500 shown in FIGS. 85Aand 85B, another exemplary node-enabled logistics receptacle isillustrated in FIGS. 86A and 86B. However, the node assembled with thereceptacle in FIGS. 86A and 86B is an ID node instead of a master node.In more detail, FIG. 86A is a diagram illustrating an exemplarynode-enabled logistics receptacle with an ID node assembled within thelogistics receptacle and ready to receive a package in accordance withan embodiment of the invention. Referring now to FIG. 86A, node-enabledlogistics receptacle 8600 is illustrated having an ID node 8605assembled within it (similar to node 8220 within receptacle 8200 shownin FIG. 82B and exemplary ID node 120 a shown in FIG. 3). In FIG. 86A,package 8235 to be shipped is outside node-enabled logistics receptacle8600 prior to depositing the package 8235 into the node-enabledlogistics receptacle 8600. Once deposited within node-enabled logisticsreceptacle 8600, FIG. 86B illustrates the package 8235 within thenode-enabled logistics receptacle 8600 in accordance with an embodimentof the invention.

In some embodiments, the package 8235 may be temporarily left in thecustody of the node-enabled logistics receptacle 8600 without beingactually within the receptacle as shown in FIG. 86B. In more detail, insome environments, the node-enabled logistics receptacle 8600 may not beable to fit the package through a package door used by customers todeposit packages within receptacle 8600. However, the node-enabledreceptacle 8600 may be able to communicate with a node package leftoutside of the receptacle—e.g., if package 8235 were deposited within asmall distance of receptacle 8600 the node 8605 may be able to detectsignals coming from the node in package 8235, associated with the nodepackage 8235, and temporarily gain a type of managerial custody of thepackage 8235. For non-node packages, the node within the node-enabledlogistics receptacle may use additional sensors discussed below withreference to FIGS. 89A-D.

In a further embodiment where no external sensors are incorporated aspart of the node-enabled logistics receptacle to sense the presence of apackage outside the receptacle, third party data may be used by theserver in predicting the likelihood of a package being left outside thenode-enabled logistics receptacle. For example, such third party datamay include information on relevant weather and crime statistics for thearea where the node-enabled logistics receptacle is located. Using suchdata, sensor inputs and drop off patterns, the server may be able topredict, for a certain day, whether to exclude that particularnode-enabled logistics receptacle from being services.

As shown in FIGS. 86A and 86B, ID node 8605 is operative to communicatewithin the wireless node network with certain network devices—e.g., withother nodes (such as ID nodes and master nodes) but cannot communicatedirectly with server 100. Thus, the exemplary node-enabled logisticsreceptacle 8600 is able to provide information related to its contentsonly through an intermediary node, such as mobile master node 8610, toserver 100. In more detail, as mobile master node 8610 approaches IDnode 8605 assembled within and part of node-enabled logistics receptacle8600, master node 8610 may be broadcasting advertising packets that aredetected by ID node 8605. Through association (e.g., a passive or activeconnection between ID node 8605 and mobile master node 8610), ID node8605 may then be able to broadcast status information related to thecontent status of the node-enabled logistics receptacle 8600. Forexample, upon detecting the advertising signal from mobile master node8610, ID node 8605 may broadcast a signal that includes statusinformation as part of the header information of the broadcastedadvertising packet from ID node 8605. Such status information mayindicate what packages are within node-enabled logistics receptacle 8600and may also include a request to pick up one or more packages withinthe receptacle generally or, in a more detailed example, withspecificity as to the required shipping courier that may service thereceptacle 8600.

While an embodiment with node-enabled logistics receptacle 8600 may waituntil a mobile master node, such as mobile master node 8610, comeswithin communication range in order to report the status information sothat such information may be uploaded to the server 100, otherembodiments where the node-enabled logistics receptacle 8500 includes amaster node 8505 may more frequently report the status informationdirectly to the server 100 without requiring an intermediary node (e.g.,a master node, or in some cases an associated ID node that forwards thestatus information as a type of shared information with another masternode, which then uploads that status information to server 100).Additionally, in situations where the likelihood of a mobile master nodepassing nearby may be lower than desired, a node-enabled logisticsreceptacle that includes a master node assembled within it may be abetter solution to be deployed than one with an ID node assembled withinit.

In one embodiment, a node-enabled logistics receptacle apparatus (suchas exemplary node-enabled logistics receptacle 8500 or 8600) canproactively report its content status and comprises a logisticsreceptacle and a node assembled with the receptacle. As shown in theexample of FIGS. 82A and 82B, the logistics receptacle can receive andtemporarily maintain a package (such as package 8235) being shipped. Thereceptacle has an entrance opening (such as opening 8205) through whichthe package is received and a temporary storage area (such as region8230) where the package is temporarily and securely maintained until anauthorized pickup.

The node assembled with the receptacle (such as node 8220, master node8505, or ID node 8605) comprises a node processing unit, a node memorystorage, and at least one communication interface. The node memorystorage is coupled to the node processing unit, and maintains code forexecution by the node processing unit along with at least a contentstatus related to one or more packages currently maintained within thelogistics receptacle. The communication interface is also coupled to thenode processing unit, and is operative to communicate with anothernetwork device (such as another node or a server) in the wireless nodenetwork.

The node processing unit, when executing the code maintained on the nodememory storage, is operative to perform various functions whenproactively reporting a content status of the node-enabled logisticsreceptacle. In more detail, the node processing unit is operative toupdate the content status stored in the node memory storage based uponwhether the logistics receptacle has received a package and istemporarily maintaining custody the package. The node processing unit isalso operative to broadcast status information over the at least onecommunication interface, where the status information relates to theupdated content status for the logistics receptacle.

In a further embodiment, the node processing unit of the node-enabledlogistics receptacle apparatus may be further operative to transmit arequest for shipping information related to the package received overthe communication interface, and may be further operative to receive therequested shipping information related to the package over thecommunication interface.

In another embodiment, the node processing unit may be further operativeto identify a shipping courier for the package from the requestedshipping information received.

In several more detailed embodiments, the status information broadcastmay comprise a request to pick up the package from the node-enabledlogistics receptacle; a request for the identified shipping courier topick up the package from the node-enabled logistics receptacle; or arequest to pick up at least one package from the node-enabled logisticsreceptacle when a number of packages temporarily maintained within thelogistics receptacle is more than a pickup threshold. Such a pickupthreshold may be, for example, a number of packages sensed to be withinthe receptacle (e.g., via node sensing, impact sensing, a combination ofnode and impact sensing, scanning as the package is inserted), a weightof the packages within the receptacle obtained via a built-in scale orweight sensor at the bottom of the interior storage region (e.g., region8230), optically detecting when packages within the region are tallerthan a predetermined threshold height using another sensor disposedwithin the interior storage region (e.g., a light beam and lightdetector).

Additionally, another embodiment of the apparatus may have the nodeprocessing unit being further operative to update the content statusstored in the node memory storage based upon whether the node processingunit detects the package has been removed from within the logisticsreceptacle. And, the node processing unit may be further operative tobroadcast updated status information over the at least one communicationinterface, where the updated status information comprises a messageindicating there is no need for a shipping courier to service thenode-enabled logistics receptacle. For example, if there are no packageswithin the node-enabled logistics receptacle, there would be no need fora shipping courier to adhere to a preexisting schedule to travel to andcheck the receptacle for packages. In a similar example, if there are nopackages within the node-enabled logistics receptacle for a particularshipping courier (i.e., the receptacle is serviced by different shippingcouriers), there would be no need for that particular shipping courierto adhere to a preexisting schedule to travel to and check thereceptacle for packages that they are responsible to pick up.

And similar to the embodiments shown in FIGS. 85A and 85B, the nodeassembled with the receptacle in the apparatus may comprise a masternode (such as master node 8505) operative to communicate directly to aserver in the wireless node network. As such, the node processing unitmay be further operative to broadcasting the status information over theat least one communication interface directly to the server in thewireless node network.

And similar to the embodiments shown in FIGS. 86A and 86B, the nodeassembled with the receptacle in the apparatus may comprise an ID nodeoperative to communicate directly to a master node in the wireless nodenetwork. As such, the node processing unit may be further operative tobroadcast the status information over the at least one communicationinterface directly to the master node in the wireless node network, withthe master node being operative to forward the status information to aserver in the wireless node network.

In another embodiment, an exemplary node-enabled logistics receptacleapparatus comprises a logistics receptacle and a node assembled with thereceptacle essential the same as that described above. However, in thisadditional embodiment, the node processing unit, when executing the codemaintained on the node memory storage, is operative to detect a signalvia the at least one communication interface, the signal having beenbroadcast from a master node in the wireless node network; access thecontent status stored in the node memory storage the node-enabledlogistics receptacle; and causing the at least one communicationinterface to broadcast status information to the master node related tothe content status for the node-enabled logistics receptacle.

Additionally, the node processing unit may be further operative torequest shipping information related to the package from the masternode. In more detail, the node processing unit may be further operativeto receive the requested shipping information related to the packagefrom the master node. In still more detail, the node processing unit maybe further operative to identify a shipping courier for the package fromthe requested shipping information received.

And in more detail, the status information may comprise a request topick up the package from the node-enabled logistics receptacle, or arequest for the identified shipping courier to pick up the package fromthe node-enabled logistics receptacle.

FIG. 87 is a flow diagram illustrating an exemplary method forproactively reporting a content status of a node-enabled logisticsreceptacle in a wireless node network in accordance with an embodimentof the invention. Referring now to FIG. 87, method 8700 begins at step8705 by updating the content status stored in memory onboard thenode-enabled logistics receptacle based upon whether the node-enabledlogistics receptacle has received a package and is temporarilymaintaining custody of the package. In a more detailed embodiment,method 8700 may also have the node-enabled logistics receptacle requestshipping information related to the package received (e.g., from amaster node or directly from a server if the receptacle is assembledwith a master node in it). Additionally, method 8700 may include thenode-enabled logistics receptacle receiving the requested shippinginformation related to the package, and identifying a shipping courierfor the package from the requested shipping information received. Forexample, a shipping courier for the package may be associated with andidentified from the shipping server selected (e.g., a very time-definiteshipping service may indicate and identify FedEx Express as the shippingcourier).

In a few more detailed embodiments, method 8700 may have the statusinformation comprising a request to pick up the package from thenode-enabled logistics receptacle; or a request for the identifiedshipping courier to pick up the package from the node-enabled logisticsreceptacle; or a request to pick up at least one package from thenode-enabled logistics receptacle when a number of packages in thetemporarily custody of the node-enabled logistics receptacle is morethan a pickup threshold.

At step 8710, method 8700 concludes by broadcasting status informationrelated to the updated content status for the node-enabled logisticsreceptacle. For example, in one embodiment this may include broadcastingthe status information from a master node in the node-enabled logisticsreceptacle directly to a server in the wireless node network. In anotherembodiment, this may involve broadcasting the status information from anID node in the node-enabled logistics receptacle directly to a masternode in the wireless node network, where the master node is operative toforward the status information to a server in the wireless node network.As such, the status information may be forwarded or otherwise uploadedto the backend server, which can then make use of such proactivereporting rather than the reactive post-visit report from courier aftera scheduled visit (which may or may not be needed).

With such updated content status information provided to the backendserver, the server can analyze the updated information, third partyweather information, crime statistics, and other sensor data and/or dropoff patterns with the particular node-enabled logistics receptacle topredict a need for pickup services. In other words, the server may usethis proactive notification of status information related to the updatedcontent status when determining whether to deploy pickup services forthe particular node-enabled logistics receptacle.

Additionally, method 8700 may also include updating the content statusstored in the memory onboard the node-enabled logistics receptacle basedupon whether the node-enabled logistics receptacle detects the packagehas been removed from within the node-enabled logistics receptacle.Furthermore, method 8700 may also include broadcasting updated statusinformation, which may comprise a message indicating there is no needfor a shipping courier to service the node-enabled logistics receptacle.

Those skilled in the art will appreciate that method 8700 as disclosedand explained above in various embodiments may be implemented onnode-enabled logistics receptacle having an ID node (such as exemplaryID node 120 a as illustrated in FIG. 3 and ID node 8605 as illustratedin FIGS. 86A and 86B) or a master node (such as exemplary master node110 a as illustrated in FIG. 4 and master node 8505 as illustrated inFIGS. 85A and 85B), running one or more parts of a control andmanagement code (such as code 325 for an ID node 8605 based node-enabledlogistics receptacle 8600 or code 425 for a master node 8505 basednode-enabled logistics receptacle 8500) to implement any of the abovedescribed functionality. Such code may be stored on a non-transitorycomputer-readable medium (such as memory storage 315 or 415 in therespective exemplary nodes). Thus, when executing such code, aprocessing unit of the node (such as unit 300 or unit 400) may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 8700 and variations of that method.

FIG. 88 is a flow diagram illustrating another exemplary method forproactively reporting a content status of a node-enabled logisticsreceptacle in a wireless node network in accordance with an embodimentof the invention. Referring now to FIG. 88, method 8800 begins at step8805 with a node assembled within the node-enabled logistics receptacledetecting a signal broadcast from a master node in the wireless nodenetwork. For example, as shown in FIG. 86B, mobile master node 8610 maybe broadcasting an advertising signal that is detected by ID node 8605assembled as part of node-enabled logistics receptacle 8600.

At step 8810, method 8800 continues by accessing the content statusstored in memory onboard the node-enabled logistics receptacle. Here,the content status indicates whether the node-enabled logisticsreceptacle has received a package and is temporarily maintaining custodyof the package. In the example shown in FIG. 86B, such content statusinformation stored in node memory storage of node-enabled logisticsreceptacle 8600 indicates a package 8235 is being maintained within thereceptacle 8600.

At step 8815, method 8800 concludes with the node assembled within thenode-enabled logistics receptacle broadcasting status information to themaster node related to the content status for the node-enabled logisticsreceptacle. For example, as shown in FIG. 86B, ID node 8605 withinreceptacle 8600 may associate with mobile master node 8610 and, as partof that association or after actively associating, broadcasts statusinformation to mobile master node 8610.

In a further embodiment, method 8800 may include requesting, from themaster node by the node assembled within the node-enabled logisticsreceptacle, shipping information related to the package. And in moredetail, method 8800 may also have the node assembled within thenode-enabled logistics receptacle receiving the requested shippinginformation related to the package. And in even more detail, method 8800may identify a shipping courier for the package from the requestedshipping information received.

And in more detailed embodiment, the status information may comprise arequest to pick up the package from the node-enabled logisticsreceptacle, or a request for the identified shipping courier to pick upthe package from the node-enabled logistics receptacle.

Those skilled in the art will appreciate that method 8800 as disclosedand explained above in various embodiments may be implemented onnode-enabled logistics receptacle having an ID node (such as exemplaryID node 120 a as illustrated in FIG. 3 and ID node 8605 as illustratedin FIGS. 86A and 86B) or a master node (such as exemplary master node110 a as illustrated in FIG. 4 and master node 8505 as illustrated inFIGS. 85A and 85B), running one or more parts of a control andmanagement code (such as code 325 for an ID node 8605 based node-enabledlogistics receptacle 8600 or code 425 for a master node 8505 basednode-enabled logistics receptacle 8500) to implement any of the abovedescribed functionality. Such code may be stored on a non-transitorycomputer-readable medium (such as memory storage 315 or 415 in therespective exemplary nodes). Thus, when executing such code, aprocessing unit of the node (such as unit 300 or unit 400) may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 8800 and variations of that method.

Node-Enabled Logistics Receptacle—Detecting Packages

In an exemplary logistics system, different types of packages may beused to ship items. For example, and as explained in several embodimentsherein, one type of package may have its own node related to it (e.g.,placed within the package, attached to the package, integrated as partof the package or the materials making up the package) and may begenerally referred to as a node package or node-enabled package. In oneexample, such a package may have a node simply placed within the packagealong with the item to be shipped. In another example, the node may beattached to, part of, integrated into, or embedded within (fully orpartially) the package or packaging materials. In contrast, another typeof package is not node-enabled. In other words, packages may includethose that are node-enabled and those that are not.

To handle aspects of shipping such diverse types of packages, anotherembodiment takes advantage of one or more features of a node-enabledlogistics receptacle to be able to detect and differentiate thedifferent types of packages. FIGS. 89A-89D show aspects and features ofdifferent embodiments of a node-enabled logistics receptacle that candetect different types of packages, while FIG. 90 explains an exemplarymethod for doing so.

In more detail, FIG. 89A is a diagram illustrating an exemplarynode-enabled logistics receptacle with a node and an exemplary sensorassembled within the logistics receptacle in accordance with anembodiment of the invention. Referring now to FIG. 89A, an exemplarynode-enabled logistics receptacle 8200 is shown in side view withinternal structure illustrated with dotted lines, similar to theembodiment shown in FIG. 82B. For ease of discussion, exemplarynode-enabled logistics receptacle 8200 shown in FIG. 89A is similar tothat as shown in FIG. 82B for elements that appear in common in bothfigures. In addition, the exemplary node 8220 within the receptacle 8200illustrated in FIG. 89A further includes one or more sensors that assistwith detecting and differentiating packages as they are deposited withinthe exemplary node-enabled logistics receptacle 8200.

In more detail as shown in the embodiment of FIG. 89A, node 8220 furtherincludes a sensor pad or plate 8915, which is coupled, via wiring 8910,to node 8220. In operation, the sensor 8915 responds to stimulus (e.g.,an impact force or weight, etc.) and produces a responsive sensorsignal, which is provided on wiring 8910 to the node processing unitwithin node 8220. As such, the embodiment of node 8220 shown in FIG. 89Ais a type of sensor node that detects the deposit of any package withinthe receptacle 8220. Thus, as one or more packages 8900, 8905 aredeposited within node-enabled logistics receptacle 8200 (e.g., depositedwithin the interior storage region 8230), an example of sensor pad/plate8915 senses an impact from the deposited package or measures the weightof the package added to within the receptacle 8200. Thus, exemplaryembodiments of sensor 8915 may be implemented as a pressure pad,pressure plate, impact sensor, or measurement scale that is responsiveto force (e.g., momentary, constant, etc.) exerted by packages depositedwithin the interior storage region 8230 of the node-enabled logisticsreceptacle 8200 against the bottom of the region 8230.

In another embodiment, such as the embodiment illustrated in FIG. 89B,node 8220 may further include a sensor 8920, which is also coupled, viawiring 8910, to node 8220 in this embodiment. In operation, the sensor8920 is typically disposed on a side wall of region 8230 where itdetects movement within a part of the node-enabled logistics receptacle8200. Thus, in one example, sensor 8920 may be a sensor that relies upona type of echolocation (e.g., ultrasonic sensor that sends outultrasonic waves to determine movement based upon a change in thereturned energy sensed by the sensor). In an example shown in FIG. 89C,sensor 8925 may be a light sensor where a package, which is moving fromthe opening 8205 and through the top interior part 8225 of receptacle8200 to enter and travel through the interior storage region 8230,breaks a light being sensed or detected by sensor 8925, which thengenerates a responsive sensor signal. Example sensors may include alight source (not shown) within the sensor or rely upon an externallight source (e.g., laser) disposed opposite the sensor 8920. In anotherembodiment, the broken light beam indicating movement within the regionof interest may simply cause a change in the signal generated by thesensor (e.g., a temporary drop in voltage indicative of the time thelight beam was broken).

Other embodiments may use sensors 8920, 8925 as band of multiple sensorsdisposed at different locations within the receptacle 8200. For example,such a band of sensors making up sensors 8920, 8925 may extend in one ormore dimensions of the region covered. Thus, such a band of sensors mayprovide more extensive coverage within regions of receptacle 8200 tobetter capture movement of a package (e.g., the deposit of any type ofpackage within receptacle 8200) or attempts to insert a package withinreceptacle 8200 (e.g., sensing movement with sensor 8925 but not sensingmovement with sensor 8920 given that the package could not fit into thereceptacle).

Additional embodiments may implement sensor 8920 with a scanner capableof capturing barcode scan information from an exterior label present onthe package being deposited. As such, node 8220 may be operative tointeract with sensor 8920 and capture scan information related to theparticular package being deposited even if the package is not anode-enabled package.

A counter (implemented as part of the circuitry that comprises node8220) may also be used in various embodiments to track the total numberof packages detected to have been deposited within the interior storageregion 8230 of node-enabled logistics receptacle 8200. Additionally, asthe receptacle 8200 is serviced by a courier, who may pick up one ormore, but potentially not all packages, the counter may be updated toreflect a change in the number of packages within the region 8230.

In still another embodiment, such as the embodiment illustrated in FIG.89C, node 8220 of exemplary node-enabled logistics receptacle 8200 mayfurther include a door sensor that detects movement of the door shown inFIG. 89C hinged to cover opening 8205. Such a sensor would be coupled,via wiring (not shown for purposes of clarity in the Figure), to node8220 in this embodiment.

In operation, the door sensor is typically disposed on a side wall ofregion 8225 where it detects movement of the door covering opening 8205via conventional contact switches or magnetic switches. Another exampleof door sensor may be incorporated as part of or within a hinge for thedoor covering opening 8205. Like sensor 8925 described above, the doorsensor may help to identify whether there are any packages placedoutside node-enabled logistics receptacle 8200 (e.g., sensing movementof the door sensor but not sensing movement with sensor 8920 within theinterior of the receptacle given that the package could not fit into thereceptacle).

Additionally, one or more external sensors may be deployed in otherembodiments to help detect one or more packages outside the receptaclebut that are temporarily in the management custody of the node-enabledlogistics receptacle while not being within region 8230. FIG. 89D is adiagram illustrating an exemplary node-enabled logistics receptacle witha node and an exemplary external sensor that may be used as part of thenode-enabled logistics receptacle in accordance with an embodiment ofthe invention. Referring now to FIG. 89D, receptacle 8200 is shown withnode 8220 as in FIGS. 89A-C. However, in FIG. 89D, node 8220 is coupledvia wiring 8935 to an external sensor 8930 that is operative to monitoran area or region near the receptacle 8220. While only one externalsensor 8930 is shown in FIG. 89D for simplicity, those skilled in theart will appreciate that other embodiments may employ multiple externalsensors to cover different, distinct, or overlapping areas or regionsnear the node-enabled logistics receptacle.

External sensor 8930 may sense (via motion detection as explained abovewith respect to sensors 8920 and 8925) the presence of package 8940. Ifpackage 8940 is detected to be within a designated area near thereceptacle 8200 for a period of time, node 8220 may consider package8940 to be within its temporary custody despite being outside thereceptacle 8200. In more detail, node 8220 may use sensor 8930 to helpkeep track of node and non-node packages deposited outside thereceptacle. Here, for example, once a certain number (such as even one)of packages are detected outside the receptacle but within the temporarycustody of the receptacle 8200, node 8220 may update the content statusfor the receptacle and broadcast status information to reflect the oneor more packages being outside the receptacle but within the temporarycustody of the receptacle.

Thus, an embodiment of the node-enabled logistics receptacle maydetermine whether the receptacle has received the package and istemporarily maintaining custody of the package based upon a detectionresult from at least one sensor deployed as part of the node-enabledlogistics receptacle, and that sensor may be implemented as an internalsensor (such as sensors 8920 and 8925), an external sensor (such as8930), a door sensor, or the like as described herein.

In another embodiment, a node-enabled logistics receptacle apparatus isdescribed for use in a wireless node network (e.g., a network of nodes,such as ID nodes and master nodes, and a server) that detects aplurality of package types. The node-enabled logistics receptacleapparatus comprises a logistics receptacle and a node assembled with thereceptacle. For example, as shown in FIGS. 82A and 82B as well as FIGS.89A and 89B, the logistics receptacle can receive and temporarilymaintain a package (such as packages 8235, 8900, and 8905) beingshipped. The receptacle has an entrance opening (such as opening 8205)through which the package is received and an internal storage region(such as region 8230) where one or more packages are temporarily andsecurely maintained until an authorized pickup.

The node assembled with the receptacle (such as node 8220 illustrated inFIGS. 89A-89D but consistent with the common structure of an ID node ora master node as illustrated and described with respect to FIGS. 3 and4) comprises a node processing unit, a node memory storage, and at leastone communication interface. The node memory storage is coupled to thenode processing unit, and maintains code for execution by the nodeprocessing unit along with logged detection information about differentpackage types within the receptacle. The communication interface is alsocoupled to the node processing unit, and is operative to communicatewith another network device (such as another node or a server) in thewireless node network.

The node processing unit, when executing the code maintained on the nodememory storage, is operative to perform various functions when detectinga plurality of package types. In more detail, the node processing unitis operative, when executing such code, to detect a first type ofpackage (a node-enabled package) by receiving a signal broadcast from anode within a first package prior to sensing a deposit of the firstpackage within the node-enabled logistics receptacle. The nodeprocessing unit is also operative to detect a second type of package(not a node-enabled package) by sensing a deposit of a second packagewithin the node-enabled logistics receptacle without receiving a signalbroadcast from a node within the second package. The node processingunit is then operative to log the detections of the first type ofpackage and the second type of package as the detection informationstored on the node memory storage, and cause the communication interfaceto transmit a notification to another network device (such as a serveror a master node) within the wireless node network about the loggeddetection of the first type of package and the second type of package.

For example, in the illustrated example of FIGS. 89A-89D, if node 8220is an ID node, then the communication interface is a shorter rangecommunication interface capable of communicating with a master node inthe hierarchy of node types within the wireless node network. However,if node 8220 is implemented as a master node, then the communicationinterface may be a longer range communication interface capable ofdirectly communicating with the server without needing an intermediarymaster node when reporting detected types of packages deposited in thenode-enabled logistics receptacle.

In a more detailed embodiment, the node processing unit may be furtheroperative to detect the first type of package by being operative toreceive, via the communication interface, the signal broadcast from thenode within the first package within a predetermined time interval priorto sensing the deposit of the first package within the node-enabledlogistics receptacle. For example, as the node-enabled packageapproaches the location of the node-enabled logistics receptacle, thenode assembled with the receptacle (e.g., node 8220) may attempt toassociate with the node-enabled package. In more detail, suchassociating may be merely a passive association where the nodeprocessing unit is not yet actively connected to the node-enabledpackage, but detects an advertising signal being broadcast from thenode-enabled package. In another example, such associating may beaccomplished with an active association that allows for an authorizedconnection between the node-enabled package and the node-enabledlogistics receptacle.

In another more detailed embodiment, the node assembled with thereceptacle may comprise a sensor (e.g., sensor 8915, sensor 8920, sensor8925, the door sensor, and/or external sensor 8930) coupled to the nodeprocessing unit. As such, the node processing unit may be furtheroperative to detect the second type of package by being operative tosense the deposit of the second package within the node-enabledlogistics receptacle based upon a sensor signal provided by the sensorto the node processing unit. For example, in the embodiment shown inFIG. 89A, node 8220 is operative to sense the deposit of a package thatis not node-enabled (e.g., package 8905) based upon a sensor signalprovided from sensor 8915 through wiring 8910 to interface circuitrywithin node 8220.

In further embodiments that are more detailed regarding the sensor, thesensor may be deployed within the internal storage region of thenode-enabled logistics receptacle. For example, the sensor may beimplemented as a motion detector coupled to the node assembled with thereceptacle. As such, the motion detector may sense movement of the firstpackage and the second package as the packages are respectivelydeposited within the interior storage region, and may provide the sensorsignal to the node processing unit related to the sensed movement. Suchan embodiment is illustrated in FIG. 89B, where sensor 8920 may detectmovement of the packages 8900, 8905 as they are deposited withininterior storage region 8230.

In another example, the sensor may be implemented as an impact sensorcoupled to the node assembled with the receptacle. As such, the impactsensor may register a change in pressure exerted against a bottomsurface of the interior storage region in response to an objectdeposited within the interior storage region, and may provide the sensorsignal to the node processing unit related to the sensed impact. Such anembodiment is illustrated in FIG. 89A, where sensor 8915 may detect animpact of each of the packages 8900, 8905 as they are deposited withininterior storage region 8230 and onto a sensor plate or pad of thesensor 8915.

In still another example, the sensor may be implemented as a measurementscale coupled to the node assembled with the receptacle. As such, themeasurement scale measures a weight of an object (such as apackage—e.g., package 8900 or 8905) deposited within the interiorstorage region and provides the sensor signal to the node processingunit related to the measured weight. Such an embodiment is illustratedwith reference to FIG. 89A, where sensor 8915 may be a scale that canincrementally weigh the packages 8900, 8905 as they are deposited withininterior storage region 8230. As each package is deposited withininterior storage region 8230 and comes to rest, the package and itembeing shipped within the package exert a force on the sensor 8915. Themeasured weight can be determined from the sensor signal sent to thenode 8220, which can keep track and log when packages are deposited andhow much they incrementally weigh so as to provide further contextualinformation regarding what is in the node-enabled logistics receptacle.

In the context of such exemplary node-enabled logistics receptacles thatcan deter different package types, FIG. 90 is a flow diagramillustrating an exemplary method for detecting a plurality of packagetypes within a node-enabled logistics receptacle in a wireless nodenetwork in accordance with an embodiment of the invention. Referring nowto FIG. 90, method 9000 begins at step 9005 by detecting a first type ofpackage by receiving a signal broadcast from a node within a firstpackage (a node-enabled package) prior to sensing a deposit of the firstpackage with the node-enabled logistics receptacle. Such a deposit maybe within the receptacle as shown in FIGS. 89A and 89B or may be in anarea monitored and near the receptacle as shown in FIG. 89C (e.g., foroversized packages where an external sensor may detect a deposit of sucha package outside the receptacle after a period of time with the packageremaining there). Those skilled in the art will appreciate that any suchdeposits are considered to have the package be with the temporarycustody of the node-enabled logistics receptacle—regardless of whetherthe deposit is within the receptacle or adjacent and outside thereceptacle.

In another embodiment, detecting the first type of package may comprisereceiving the signal broadcast from the node within the first packagewithin a predetermined time interval prior to sensing the deposit of thefirst package within the node-enabled logistics receptacle. In moredetail, the step of receiving the signal broadcast from the node withinthe first package may be accomplished by associating the node within thefirst package with the node assembled within the node-enabled logisticsreceptacle.

At step 9010, method 9000 continues by detecting a second type ofpackage by sensing a deposit of a second package (not a node-enabledpackage) within the node-enabled logistics receptacle without receivinga signal broadcast from a node within the second package. Anotherembodiment of method 9000 may detect a second type of package by sensingthe deposit of the second package outside the node-enabled logisticsreceptacle without receiving a signal broadcast from the second package.Thus, sensing the deposit of the second package may simply be that thedeposit is to the temporary custody of the node-enabled logisticsreceptacle (either within the receptacle or in an area near to butoutside the receptacle).

As such, method 9000 is able to detect both node-packages and packagesthat include those that are not node-packages. In another embodiment,detecting the second type of package may further comprise sensing thedeposit of the second package within the node-enabled logisticsreceptacle using a sensor coupled to a node assembled within thenode-enabled logistics receptacle. Such a sensor may be deployed withinan interior storage region of the node-enabled logistics receptacle.

In general, the sensor may take several exemplary forms—such as aninternal sensor, an external sensor or a door sensor (e.g., as shown inFIGS. 89A-89D). In more detail, the sensor may comprise at least one ofan internal sensor disposed within the internal storage region of thereceptacle, an external sensor that monitors an area outside but nearthe logistics receptacle, and a door sensor that monitors the entranceopening of the receptacle (typically covered by a door). In a moredetailed example, the sensor may comprise a motion detector coupled tothe node assembled within the node-enabled logistics receptacle. Assuch, the motion detector may sense movement of the first package andthe second package when deposited within the interior storage region ofthe node-enabled logistics receptacle and may provide the sensor signalto the node processing unit related to the sensed movement.

In another example, the sensor may comprise an impact sensor coupled tothe node assembled within the node-enabled logistics receptacle. Assuch, the impact sensor may register a change in pressure or forceexerted against a bottom surface of the interior storage region inresponse to an object deposited within the interior storage region andmay provide the sensor signal to the node processing unit related to thesensed impact.

In still another example, the sensor may comprise a measurement scalecoupled to the node assembled within the node-enabled logisticsreceptacle. As such, the measurement scale may measure a weight of anobject (such as a package) deposited within the interior storage regionand may provide the sensor signal to the node processing unit related tothe measured weight.

At step 9015, method 9000 continues by logging the detections of thefirst type of package and the second type of package. In one embodiment,the detections are logged in memory, such as memory storage in node 8220of FIGS. 89A and 89B. With this logged information on detections ofnode-enabled packages and detections of packages that are notnode-enabled (e.g., based on a difference between the detected depositsof all packages and subtracting out those that are confirmed to benode-enabled packages via the signal detection or association).

And so at step 9020, method 9000 concludes by notifying another networkdevice within the wireless node network about the logged detection ofthe first type of package and the second type of package. For example,if the node assembled within the node-enabled logistics receptacle isimplemented with an ID node, the other network device may be a masternode, which can receives the notification and forward a message to theserver regarding the logged detections as necessary or desired.Alternatively, should the node assembled within the node-enabledlogistics receptacle is implemented with a master node, greateropportunities are presented to directly communicate logged detections tothe server rather than need to involve an intermediary node, such asanother master node.

Those skilled in the art will appreciate that method 9000 as disclosedand explained above in various embodiments may be implemented onnode-enabled logistics receptacle having a node (such as exemplary IDnode 120 a as illustrated in FIG. 3, exemplary master node 110 a asillustrated in FIG. 4, or node 8220 as illustrated in FIGS. 89A and89B), running one or more parts of a control and management code (suchas code 325 or code 425) to implement any of the above describedfunctionality. Such code may be stored on a non-transitorycomputer-readable medium (such as memory storage 315 or 415 in therespective exemplary nodes). Thus, when executing such code, aprocessing unit of the node (such as unit 300 or unit 400) may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 9000 and variations of that method.

Deployment of Pickup Services with Multiple Pickup Entities

In another exemplary logistics system, an exemplary node-enabledlogistics receptacle may have packages in its temporary custody that areintended to be serviced for pickup by more than one pickup entity. Forexample, a first shipping customer may desire and pay for shipping afirst package by a particular pickup entity, such as FedEx® Express,while another shipping customer may desire and pay for shipping anotherpackage by a different pickup entity, such as FedEx® Ground. Generally,an approach to servicing the packages deposited and temporarilymaintained in a conventional logistics receptacle (such as a drop box orsecure locker unit) involves an existing schedule where one or morepickup entities (e.g., a shipping courier) travels to the receptacle toperform a pickup service on packages in the receptacle. This may be timeconsuming and unpredictable. Additionally, it typically leads tounnecessary trips at times for a particular pickup entity and wastefulof the entity's resources.

In some instances, things are complicated even more where a receptaclemay not be serviced by more than one pickup entity. This may require theshipping customer dropping off a package to be shipped to find anappropriate location that can be serviced by that particular pickupservice, even when multiple pickup services are available as a way toprovide the customer a selection of shipping options from one shippingentity. From the shipping entity's perspective, requiring a differentreceptacle for each pickup entity is also wasteful. And simply puttingall packages into a common receptacle without more incurs time consumingwork for each different pickup service entity sending a courier to pickup their specific packages from the common receptacle.

In another embodiment, a node-enabled logistics receptacle (e.g.,node-enabled drop box or node-enabled locker unit) so that packages maybe dropped for shipping and picked up by multiple pickup entities fromthe same receptacle in a more efficient and enhanced manner. FIG. 91 isa diagram illustrating an exemplary node-enabled logistics receptaclethat reports a current status of packages maintained within thereceptacle to a server for enhanced deployment of pickup services bypickup entities in accordance with an embodiment of the invention.Referring now to FIG. 91, an exemplary node-enabled logistics receptacle9100 is illustrated in communication with server 100 over network 105.Such an exemplary node-enabled logistics receptacle 9100 is similar tothat as described and shown in other figures (e.g., FIGS. 82A, 82B, 85A,85B, 86A, 86B, 89A, 89B). And as shown in FIG. 91, exemplary nodeenabled logistics receptacle 9100 includes a node (e.g., master node9105) assembled with the receptacle itself, and is temporarilymaintaining two packages (e.g., package 9110, package 9115).

The exemplary node-enabled logistics receptacle 9100 is operative,through code running on the processing unit of master node 9105, to senda message to server 100 to report the current status of packages in thereceptacle 9100. In more detail, node-enabled logistics receptacle 9100is operative, through code (such as code 425) running on the processingunit (such as unit 400) of master node 9105, to send a message to server100 where the message identifies a plurality of packages (such aspackages 9110, 9115) currently maintained within the node-enabledlogistics receptacle 9100 ready for pickup. The message is transmittedthrough a communication interface that is part of master node 9105,through network 105, and is received by server 100.

Exemplary server 100, as explained in more detail with respect to FIG.5, is an apparatus that includes at least one server processing unit(such as processing unit 500), at least one server memory storage (suchas memory storage 515), and a communication interface (such as networkinterface 590). As explained above with reference to FIG. 5, server 100may be implemented as a single computing system, a distributed server(e.g., separate servers for separate server related tasks), ahierarchical server (e.g., a server implemented with multiple levelswhere information may be maintained at different levels and tasksperformed at different levels depending on implementation), or a serverfarm that logically allows multiple distinct components to function asone server computing platform device from the perspective of a clientdevice (e.g., devices 200, 205 or master node 110 a). In someembodiments, an exemplary server may include one or more serversdedicated for specific geographic regions as information collectedwithin different regions may include and be subject to differentregulatory controls and requirements implemented on respective regionalservers. Likewise, while the embodiment shown in FIG. 5 illustrates asingle memory storage 515, exemplary server 100 may deploy more than onememory storage media. And memory storage media may be in differingnon-transitory forms (e.g., conventional hard disk drives, solid statememory such as flash memory, optical drives, RAID systems, cloud storageconfigured memory, network storage appliances, etc.).

Additionally, the exemplary server apparatus' memory storage is coupledto the server processing unit. While not shown in FIG. 91 (but shown aspart of exemplary server 100 illustrated in FIG. 5), the server memorystorage in server 100 maintains code for execution by the serverprocessing unit. Additionally, server memory storage may maintainshipping information 9120 about a plurality of packages (such aspackages 9110, 9115) currently maintained within the node-enabledlogistics receptacle 9100 ready for pickup.

The communication interface of the server apparatus is coupled to theserver processing unit and is operative to communicate with at least thenode-enabled logistics receptacle in the wireless node network. Forexample, the network interface 590 of exemplary server 100 shown in FIG.5 is a type of communication interface that is coupled to processingunit 500 and, as shown in FIG. 91, is operative to communicate overnetwork 105 with at least node-enabled logistics receptacle 9100 as wellas other network devices in a wireless node network (e.g., other masternodes) and other servers or computing devices that are capable ofcommunicating over network 105.

The server processing unit of the server apparatus, when executing thecode maintained on the server memory storage, is operative to performcertain functions that allow for deploying a plurality of pickupentities to a node-enabled logistics receptacle (such as receptacle9100) in a wireless node network. In more detail, the processing unit,when executing the code, is operative to receive a message from thenode-enabled logistics receptacle over the communication interface wherethe message identifies a plurality of packages currently maintainedwithin the node-enabled logistics receptacle ready for pickup. Forinstance, in the illustrated example of FIG. 91, the processing unit ofserver 100 may be operative to receive a message prepared andtransmitted by master node 9105 within node-enabled logistics receptacle9100. Such a message identifies package 9110 and package 9115 as beingcurrently maintained within the node-enabled logistics receptacle 9100and ready for pickup.

The processing unit, when executing the code, is also operative toaccess the server memory storage to obtain shipping information relatedto the identified plurality of packages currently maintained with thenode-enabled logistics receptacle. For example, server 100 may accessshipping information 9120, which is information related to shipping ofpackages 9110 and 9115.

From this proactive notification facilitated by the node-enabledlogistics receptacle, the processing unit, when executing the code, isthen operative to identify which of the plurality of pickup entitiesneed to be deployed to provide one or more pickup services at thenode-enabled logistics receptacle based upon the shipping information.For example, the shipping information 9120 relating to package 9110 mayidentify FedEx® Express as the appropriate pickup entity to provide apickup service for package 9110 at receptacle 9100 while the information9120 relating to package 9115 may identify FedEx® Ground as theappropriate pickup entity to provide a pickup service for package 9115at receptacle 9100.

In one embodiment, the server processing unit may be further operativeto cause the communication interface to transmit a pickup request to theidentified ones of the pickup entities regarding the one or more pickupservices to be performed at the node-enabled logistics receptacle.Accordingly, in the example shown in FIG. 91, server 100 may transmitthe pickup request to a courier vehicle 9135 given FedEx® Express wasone of the identified pickup entities that needs to pick up a package(e.g., package 9110) at node-enabled logistics receptacle 9100.Likewise, server 100 may transmit the pickup request to another couriervehicle 9140 given FedEx® Ground was another of the identified pickupentities that needs to pick up a package (e.g., package 9115) atnode-enabled logistics receptacle 9100.

In another embodiment, the server processing unit may be furtheroperative to update historic data for the node-enabled logisticsreceptacle related to the identified ones of the pickup entities, andstore the updated historic data in the server memory storage. Asexplained earlier with respect to FIG. 5, historic data is generallydata previously collected and/or analyzed related to a commoncharacteristic. Historic data 575 embodies operational knowledge andknow-how for a particular characteristic relevant to operations of thewireless node network. Here, exemplary historic data relates to whatpickup entities are needed for packages deposited in a particularreceptacle. Accordingly, in the example shown in FIG. 91, server 100 mayupdate such historic data 575 for the node-enabled logistics receptacle9100 related to the identified ones of the pickup entities (e.g., FedEx®Express and FedEx® Ground), and store the updated historic data 575 inthe server memory storage within server 100.

In still another embodiment, the server processing unit may be furtheroperative to predict a future pickup schedule for the node-enabledlogistics receptacle based upon the updated historic data. For example,as shown in FIG. 91, server 100 may predict a future pickup schedule9130 for the node-enabled logistics receptacle 9100 based upon theupdated historic data 575. Thus, the more packages are deposited thatrequire pickup service at a particular node-enabled logistics receptacleby a particular pickup entity, the more the server is able to learn fromthe proactive notifications from the particular node-enabled logisticsreceptacle.

In a further embodiment, the server processing unit may be furtheroperative to cause the future pickup schedule to be transmitted over thecommunication interface to those of the pickup entities having apredicted pickup service in the future pickup schedule for thenode-enabled logistics receptacle. In this way, the advantage of theproactive notifications from the particular node-enabled logisticsreceptacle may be leveraged in an even more broad way.

In some embodiments, server 100 may have an existing schedule 9125 ofwhich pickup entities are scheduled to provide pickup services for aparticular receptacle. As such, the server processing unit may befurther operative to notify a previously scheduled one of the pickupentities over the communications interface if the previously scheduledone of the pickup entities is not one of the identified ones of thepickup entities regarding the one or more pickup services to beperformed at the node-enabled logistics receptacle. For example, asshown in FIG. 91, server 100 may contact a pickup entity, such as FedEx®Home Delivery (e.g., via a message to a previously designed couriervehicle 9145 for that pickup entity) to let it know that it no longerneeds to perform pickup services at node-enabled logistics receptacle9100. So, as shown in FIG. 91, courier vehicle 9145 for FedEx® HomeDelivery can avoid wasting time, effort, and cost of an unnecessary stopand continue to another stop to pick up or drop off other packages.

In a more detailed embodiment, the server processing unit may be furtheroperative to cause the communication interface on the server to transmitthe pickup request by being operative to access an existing pickupschedule (such as schedule 9125) maintained in the server memorystorage. In more detail, the existing pickup schedule may comprise oneor more existing scheduled pickup services at the node-enabled logisticsreceptacle. The server processing unit may then be operative to notify(using the server's communication interface) one of the pickup entitiesthat is on the existing pickup schedule (e.g., schedule 9125) but thatis not currently identified as one of the plurality of pickup entitiesthat they do not need to provide one or more pickup services at thenode-enabled logistics receptacle based upon the shipping information9120.

Further, an additional embodiment may have the server processing unitbeing operative to revise the existing pickup schedule 9125 based on theidentified ones of the plurality of pickup entities that need to provideone or more pickup services at the node-enabled logistics receptaclebased upon the shipping information.

While FIG. 91 and the above description focus on the server apparatusand its operation with node-enabled logistics receptacle 9100 whendeploying various pickup entities, FIG. 92 is a flow diagramillustrating an exemplary method deploying a plurality of pickupentities to a node-enabled logistics receptacle in a wireless nodenetwork in accordance with an embodiment of the invention. Referring nowto FIG. 92, method 9200 begins at step 9205 with a server in thewireless node network receiving a message from a node-enabled logisticsreceptacle. The message identifies a plurality of packages currentlymaintained within the node-enabled logistics receptacle ready forpickup.

At step 9210, method 9200 continues by accessing shipping informationfrom a server memory storage. The shipping information is related to theidentified plurality of packages currently maintained with thenode-enabled logistics receptacle.

At step 9215, exemplary method 9215 concludes by identifying which ofthe plurality of pickup entities need to be deployed to provide one ormore pickup services at the node-enabled logistics receptacle based uponthe shipping information.

In a further embodiment, method 9200 may also include the step oftransmitting a pickup request by the server over a communicationinterface of the server to the identified ones of the pickup entitiesregarding the one or more pickup services to be performed at thenode-enabled logistics receptacle. For instance, in the exampleillustrated and explained in FIG. 91, if the identified ones of thepickup entities that need to perform pickup services at node-enablelogistics receptacle 9100 are the pickup entities FedEx® Express andFedEx® Ground (that respectively operate courier vehicles 9135 and9140), server 100 may transmit a pickup request to each of thesevehicles via network 105.

In a more detailed embodiment, method 9200 may transmit the pickuprequest by accessing an existing pickup schedule maintained in theserver memory storage, where the existing pickup schedule comprising oneor more existing scheduled pickup services at the node-enabled logisticsreceptacle. Then, method 9200 may notify one of the pickup entities thatis on the existing pickup schedule but that is not identified as one ofthe plurality of pickup entities that it does not need to provide one ormore pickup services at the node-enabled logistics receptacle based uponthe shipping information. Further still, method 9200 may also includerevising the existing pickup schedule based on the identified ones ofthe plurality of pickup entities that need to provide one or more pickupservices at the node-enabled logistics receptacle based upon theshipping information.

In yet another embodiment, method 9200 may include updating historicdata for the node-enabled logistics receptacle related to the identifiedones of the pickup entities, and predicting a future pickup schedule forthe node-enabled logistics receptacle based upon the updated historicdata. In more detail, method 9200 may also involve transmitting thefuture pickup schedule to those of the pickup entities having apredicted pickup service in the future pickup schedule for thenode-enabled logistics receptacle.

In still another embodiment, method 9200 may also include notifying apreviously scheduled one of the pickup entities if the previouslyscheduled one of the pickup entities is not one of the identified onesof the pickup entities regarding the one or more pickup services to beperformed at the node-enabled logistics receptacle.

Those skilled in the art will appreciate that method 9200 as disclosedand explained above in various embodiments may be implemented on servernetwork device (such as exemplary server 100 as illustrated in FIG. 5and as illustrated in FIG. 91), running one or more parts of a servercontrol and management code (such as code 525) to implement any of theabove described functionality. Such code may be stored on anon-transitory computer-readable medium (such as memory storage 515).Thus, when executing such code, one or more processing units of theserver (such as processing unit 500) may be operative to performoperations or steps from the exemplary methods disclosed above,including method 9200 and variations of that method.

Shipment Merging for Multi-part Shipments

In some examples, an item to be shipped may be part of a multiplepackage shipment (also referred to as a multi-part shipment, multi-pieceshipment, or MPS). In general, an MPS involves a set of items beingshipped to the same location. For example, the set of items may be a setof related items (such as parts to a desktop computer—e.g., a display, akeyboard and mouse, and a desktop computer chassis having a powersupply, disk drives, graphics boards, peripheral interfaces, and amotherboard). Each item in the set may be separately packaged. Someitems may be purchased as off the shelf items, and then included in theset of items as a re-sold item by the set supplier (e.g., a computermanufacturer). And even when a single entity manufactures each item inthe set, there are instances when separately packaging each item is costeffective and desired.

As is often the case with a set of shipped items, it may be desired forthe items to be delivered together. For example, if one of the items inthe set is missing (such as a display from an ordered computer), therest of the items in the set may be of little use to the recipient untilthat last item arrives. Indeed, there are instances (such as forpurposes of clearing a customs holding area) where further movement ordelivery of a set of items may be delayed when one or more items in theset become separated during the shipment process.

In an embodiment, various nodes in a wireless node network may bedeployed to help facilitate the potential for a quicker and moreefficient shipment of a set of items. For example, a shipping customermay deposit the set of packaged items (with each packaged item having arelated node) with a shipping company so that the set is shipped to adestination. In one embodiment, all items in the set enter a shippingoperation at the same time with their respective shipping informationidentifying each item in the set. However, in another embodiment theitems may enter the shipping operation at differing times but still haveshipping information identifying each item in the set.

FIG. 34C provides an illustration of an exemplary mid-shipment stage ina shipping and logistics operation. Referring now to FIG. 34C, a set ofpackages 130 a-130 d is illustrated as having arrived or approaching anexemplary shipment facility 3425. Each of the packages 130 a-130 dincludes a related ID node 120 a-120 d, respectively. In each of thepackages 130 a-130 d is an item that is part of a set of items shipped.Thus, the related ID nodes 120 a-120 d represent a group of ID nodeswhere reach ID node is related to a different packaged item in the set.

As shown in the embodiment of FIG. 34C, one item from the set is inpackage 130 a with ID node 120 a. That package 130 a and ID node 120 aare currently located in a vehicle 3435 approaching facility 3425, wherethe remaining packages 130 b-130 d in the set are currently located inthe exemplary shipping facility 3425 during transit to the set'sdestination. The vehicle 3435 has a vehicle master node 110 c, while thefacility 3425 has a facility master node 3430. In one example, facility3425 has numerous master nodes deployed within and around it, but suchother master nodes are not shown in FIG. 34C. Likewise, in such anexample, facility master node 3430 may be associated with a particularpart of the facility, such as a holding or containment area 3436 (suchas a customs holding area) within facility 3425. Those skilled in theart will appreciate that while holding area 3426 may be explained interms of temporarily holding packaged items for purposes of customs,other types of storage areas, receptacles, or general containments maysimilarly operate to temporarily maintain packaged items in a separateregion (e.g., area of a loading dock, storage facility, warehouse, asecured room, a special fenced area, etc.) for other purposes as part ofshipping a set of packaged items to a common destination.

FIG. 39 is a flow diagram illustrating an exemplary method for shipmentmerging of a set of items being shipped using a wireless node network.Referring now to FIG. 39, method 3900 begins at step 3095 with themaster node receiving ID node identification information from theserver. The ID node identification information defines the group of IDnodes where each ID node from the group is related to a different itemin the set of items being shipped. In one example, the ID nodeidentification information may be derived from and be part of shippinginformation related to the set of items being shipped (such as shippinginformation related to packages 130 a-130 b and their respectivelyidentified ID nodes 120 a-120 d as shown in FIG. 34C).

In one embodiment, the master node may be associated with a containment.For example, the containment may be a holding area, such as a customsholding area. In another example, the containment is merely a designatedpart of a facility or, more specifically, as secured portion of afacility.

At step 3910, method 3900 continues by associating each of the ID nodesin the group of ID nodes with the master node when the master nodedetects a signal from each of the ID nodes in the group as each of theID nodes in the group approaches the master node. In one example,associating may be implemented by establishing a passive associationbetween the master node and each of the ID nodes in the group of IDnodes without requiring an authorized connection between the master nodeand each of the ID nodes in the group of ID nodes. However, in anotherexample, associating may be establishing an active association thatreflects an authorized connection.

At step 3915, the master node transmits a notification to the serverwhen a last one of the ID nodes in the group is detected to beapproaching the master node.

At step 3920, the master node receives a shipment merge indication fromthe server. The shipment merge indication reflects that the set of itemshas been merged to a single shipment. For example, the shipment mergeindication may be an authorization for the set of items to be releasedfrom the containment. In another example, this authorization may be acustoms clearance notification authorizing release of the set of itemsfrom the containment as a single merged shipment.

In a further embodiment, such an authorization may be the result of oneor more prompted messages. In more detail, method 3900 may includegenerating an authorization prompt message by the master node, where theauthorization prompt requests an authorization for the set of items tobe released from the containment. The master node may then transmit theauthorization prompt message to another network device in the wirelessnode network (e.g., a user access device, such as a laptop computer,operated by personnel that manage the containment). The master node maythen receive the authorization in response to the authorization promptmessage.

And as a result of receiving the shipment merge indication, the method3900 may also instruct each of the ID nodes in the group to storecustoms information (such as information related to the shipment mergeindication, authorization to be released from the containment, thecustoms clearance notification, or any other customs related paperworkand related duties and fees) in a memory of the respective each of theID nodes in the group of ID nodes.

In one embodiment, the method 3900 may also include disassociating eachof the ID nodes in the group of ID nodes from the master node after themaster node determines a collective location of the group of ID nodes isoutside a predetermined vicinity of the containment and after the masternode receives the shipment merge indicator. In the example of FIG. 34C,once packages 130 a-130 d (and their related ID nodes 120 a-120 d) aremoved outside a predetermined boundary of the containment area 3426 butmaster node 3430 has received the shipment merge indication from server100, it is permitted for the set of packages 130 a-130 d to move on andbe disassociated with facility master node 3430.

However, in another embodiment, when any of the ID nodes in the group ofID nodes are detected by the master node as being located outside of thecontainment after the master node receives the shipment mergeindication, the master node may notify the server. The server mayfollow-up to locate the detected ID node and alert appropriate personnelor other systems as a way of causing local follow-up actions in facility3425 relative to that detected ID node.

Those skilled in the art will appreciate that method 3900 as disclosedand explained above in various embodiments may be implemented on a node,such as an exemplary master node as illustrated in FIG. 4, running oneor more parts of their respective control and management code 425 toimplement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium, such as memorystorage 415 within an exemplary master node. Thus, when executing suchcode, a processing unit within the respective node may be operative toperform operations or steps from the exemplary methods disclosed above,including method 3900 and variations of that method.

While FIG. 39 describes operations of an exemplary method for shipmentmerging from the perspective of exemplary master node operations, suchas facility master node 3430 in FIG. 34c , operations of shipmentmerging in another embodiment may also be explained from the perspectiveof exemplary ID node operations. FIG. 40 is a flow diagram illustratinganother exemplary method for shipment merging of a set of items beingshipped using a wireless node network. Referring now to FIG. 40, method4000 begins at step 4005 by receiving ID node identification informationfrom the master node. The ID node identification information defines thegroup of ID nodes and each ID node from the group is related to adifferent item from the set of items being shipped. In one example, theID node identification information may be derived from and be part ofshipping information related to the set of items being shipped (such asshipping information related to packages 130 a-130 b and theirrespectively identified ID nodes 120 a-120 d as shown in FIG. 34C).

At step 4010, scanning, by one ID node of the group of ID nodes, for aneighboring node. In the FIG. 34C example, ID node 120 b may scan itsgeneral vicinity for any close ID nodes within communication range(e.g., a type of neighboring node).

At step 4015, the ID node from the group detects a signal from theneighboring node and at step 4020, it can determine if the detectedneighboring node is part of the group of ID nodes based upon the signalbroadcast from the neighboring node. In the example illustrated in FIG.34C, ID node 120 b may detect neighboring nodes 120 c and 120 d, whichare identified as part of the group of nodes related to the set ofpackages 130 a-130 d being shipped. However, ID node 120 b may not yetdetect node 120 a, which is in vehicle 3435. Thus, ID nodes 120 b-120 dmay be aware that one ID node (and its related item in the package) fromtheir group is missing.

At step 4025, as a last one of the ID nodes in the group of ID nodes isdetected to be the neighboring node, method 4000 notifies a master nodeto instruct the server that the last one of the ID nodes in the group ofID nodes is approaching the ID node. Thus, in the FIG. 34C example, IDnode 120 b may detect a last of the ID nodes in the example group (i.e.,ID node 120 a) is approaching ID node 120 b. Upon this detection andrecognition that ID node 120 a is the last of the group to be detectedas a neighboring node (e.g., from the advertising signal broadcast by IDnode 120 a as it comes within communication range of ID node 120 b), IDnode 120 a (or another of the ID nodes in the group that are associatedwith facility master node 3430) may notify facility master node 3430.

At step 4030, the master node responds by sending a shipment mergeindication that is received by the ID nodes from the group. In oneexample, one of the ID nodes from group receives the shipment mergeindication, and can let others of the ID nodes from the group know ofthis (e.g., via secure information sharing between connected nodes). Theshipment merge indication reflects that the set of items has been mergedto a single shipment. In another example, the shipment merge indicationmay be an authorization for the set of items to be released from thecontainment. In yet another example, this authorization may be a customsclearance notification authorizing release of the set of items from thecontainment as a single merged shipment.

And as a result of receiving the shipment merge indication, the methodmay have one or more of the ID nodes in the group storing customsinformation (such as information related to the shipment mergeindication, authorization to be released from the containment, thecustoms clearance notification, or any other customs related paperworkand related duties and fees) in a memory of the respective each of theID nodes in the group of ID nodes.

Those skilled in the art will appreciate that method 4000 as disclosedand explained above in various embodiments may be implemented on a node,such as an exemplary ID node as illustrated in FIG. 3, running one ormore parts of their respective control and management code 325 toimplement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium, such as memorystorage 315 within an exemplary ID node. Thus, when executing such code,a processing unit 300 within the respective node may be operative toperform operations or steps from the exemplary methods disclosed above,including method 4000 and variations of that method.

Delivery Notification Using a Wireless Node Network

As an item being shipped and its related node (e.g., an ID node or amobile master node) transit a shipping path from an origin to adestination, the intended recipient awaits the item. In one example,such as that shown in FIG. 34D, an exemplary delivery point stage of ashipping operation is illustrated where an embodiment may facilitatedelivery to a fixed type of delivery point (e.g., a mailroom) and issuea notification to the intended recipient using a wireless node network.In general with reference to FIG. 34D, an exemplary delivery point 3440is shown associated with a master node 3445, which is in communicationwith server 100. Package 130 and related ID node 120 a are initiallyassociated with courier master node 110 h (also operative to communicatewith server 100). As the packaged item 130 and ID node 120 a approachthe delivery point (with master node 3445 being located substantiallynear to the delivery point 3440), master node 3445 may detectadvertising signals from ID node 120 a. Based on those signals, masternode 3445 may determine shipping information related to the approachingID node 120 a, and be able to notify an intended recipient of package130 when the ID node 120 a is substantially near the delivery point3440.

FIG. 41 is a flow diagram illustrating an exemplary method for deliverynotification using a wireless node network in accordance with anembodiment of the invention. Method 4100 begins at step 4105 where themaster node detects a signal from the ID node (e.g., ID node 120 arelated to an item being shipped in package 130) as the ID nodeapproaches the master node located substantially near a delivery point.While package 130 is shown with related ID node, an embodiment mayimplement such an ID node with a mobile master node temporarilyoperating as an ID node (for example, when the mobile master node isindoors and no longer receives satellite location signals but remainsoperative as a node in the wireless node network nonetheless).

An exemplary delivery point in this embodiment may take various forms.For example, in one embodiment, the delivery point may be a designatedshipping area, delivery area, or a general package handling area.Further, other examples of an exemplary delivery point may include alogistics receptacle, such as a controlled access locker system. Andadditional examples may have the delivery point being indoors oroutdoors.

In one example, the signal detected may be an advertising signal fromthe ID node. In the more detailed example of FIG. 34D, ID node 120 a maybe placed in an advertising mode by courier master node 110 h so that asID node 120 a approaches the delivery point 3440, ID node 120 a maybegin advertising with broadcasted signals having status andidentification information within the header of such broadcastedadvertising signals. With master node 3445 substantially near thedelivery point 3440, master node 3445 is able to scan for signalsbroadcast from approaching ID nodes (such as ID node 120 a) and maydetermine the identification of the ID node based upon the broadcastsignal from the ID node. In a further embodiment, server 100 mayinstruct courier master node 110 h when to have ID node 120 a beginbroadcasting signals and may instruct master node 3445 when to beginscanning for ID node 120 a.

The delivery point 3440 in this illustrated example may generally be adesignated shipping area that handles receipt of shipped items (such aspackage 130). In a more detailed example, delivery point 3440 may beimplemented as a mailroom of a business office or a designated drop offpoint at a facility (e.g., a loading dock where vehicles transferpackaged items being shipped, a storage room that may temporarilymaintain packaged items being shipped, a shipping desk staffed withshipping personnel responsible for further distribution of a packageditem, a mobile pickup vehicle (autonomous or driven by personnel)responsible for further distribution of a packaged item within thefacility. Those skilled in the art will appreciate that, in oneembodiment, a delivery point may generally be near a final shippingdestination (such as that illustrated in FIG. 34D where the finaldestination is the location of delivery point 3440 where an intendedrecipient may pick up the shipped item). Likewise, those skilled in theart will appreciate that the same principles may apply to an embodimentwhere the delivery point may be an intermediate shipping transfer pointin the overall shipping path for a packaged item being shipped (such asthe containment area 3426 within facility 3425 shown in FIG. 34C andwhere the intended recipient may be personnel in charge of containmentarea 3426).

At step 4110, the master node determines shipping information related tothe ID node and an intended recipient of the item being shipped. In oneexample, the master node may determine the shipping information basedupon the identification of the ID node (e.g., using the broadcast signalheader information broadcast from ID node 120 a). In one embodiment, theshipping information related to the ID node approaching may already beresident on the master node. In such a situation, server 100 may havetransmitted the relevant shipping information for package 130 and IDnode 120 a to master node 3445 as pre-staged shipping information(identifying at least the intended recipient and how to notify thatentity) before ID node 120 a is detected as approaching. This pre-stagedshipping information may be part of a larger amount of shippinginformation for multiple ID nodes (and their related items beingshipped) or may be specific pre-staged shipping information limited tothe particular ID node anticipated by the server to be approaching(which may require less memory storage requirements on the master node).However, in another embodiment, the shipping information may not bealready resident on the master node. In that situation, upon detectionof the signal from the approaching ID node, the master node may requestshipping information from the server by notifying the server that themaster node and approaching ID node are now associated (e.g., anestablished passive association without requiring an authorizedconnection between the master node and ID node, or an established activeassociation reflecting an authorized connection between the master nodeand ID node), and receiving shipping information from the server inresponse. Thus, the master node may determine the appropriate shippinginformation using the ID node identification, and may involve requestingthe shipping information from the server if it is not already residenton the master node.

At step 4115, the master node transmits a notification to the identifiedrecipient. The notification informs the identified recipient about theitem being substantially near the delivery point. Notification may be ina variety of forms and formats, such as but not limited to an emailmessage, a text message, an audio message, visual indicator, or otheralert type of communication.

In one example, transmitting the notification to the identifiedrecipient may be directly accomplished between the master node and theintended recipient. For instance, in the example of FIG. 34D, masternode 3445 may broadcast a message directly to an intended recipient,such a recipient identified by the shipping information as having a useraccess device (e.g., smartphone 205) registered in a profile fordelivery notification. Master node 3445 may be able to communicatedirectly with smartphone 205 via one of a variety of communication pathsdirectly with master node 3445 (e.g., Wi-Fi, Bluetooth, etc.). Inanother example, transmitting the notification to the identifiedrecipient may be indirectly accomplished between the master node and theintended recipient via, for example, the server. For instance, withreference to the example shown in FIG. 34D, master node 3445 may forwardthe notification to the server 100, which causes the server 100 to sendthe notification to the intended recipient via smartphone 205.

The method may also, in another embodiment, have the master nodedetermine that the ID node is within a predetermined range of thedelivery point by instructing the ID node to alter an RF transmissionpower level as the ID node approaches the delivery point beforetransmitting the notification to the intended recipient. For example,the server may be able to dynamically set the predetermined range of thedelivery point based upon context data (such as the layout of thefacility where the delivery point is located). For instance, server 100may configure master node 3445 to use a 25 foot range from the locationof the ID node 120 a to the delivery point 3440 as a notificationthreshold. Thus, master node 3445 may instruct ID node 120 a to altersignals broadcast from the ID node 120 a as the node approaches deliverypoint 3440, and master node 3445 will notify the intended recipient whenit determines ID node 120 is within the threshold 25 foot range from thedelivery point 3440. As such, the server is able to adjust and adaptbased upon, for example, what courier is dropping off ID node 120 or howfast it is anticipated that courier will move (e.g., a type of contextdata).

Those skilled in the art will appreciate that method 4100 as disclosedand explained above in various embodiments may be implemented on a node,such as an exemplary master node as illustrated in FIG. 4 or master node3445 illustrated in FIG. 34D, running one or more parts of a control andmanagement code 425 to implement any of the above describedfunctionality. Such code may be stored on a non-transitorycomputer-readable medium, such as memory storage 415 within an exemplarymaster node. Thus, when executing such code, a processing unit 400within the respective master node may be operative to perform operationsor steps from the exemplary methods disclosed above, including method4100 and variations of that method.

In more detail, another embodiment may include a master node fordelivery notification. The exemplary master node may comprise a nodeprocessing unit and a node memory storage coupled to the node processingunit. The node memory storage maintains code for execution by the nodeprocessing unit and shipping information related to an ID node and arelated item being shipped. The exemplary master node also comprisesfirst and second communication interfaces each of which being coupled tothe node processing unit. The first communication interface beingoperative to communicate with the ID node while the second communicationinterface is operative to communicate with the server.

When executing the code maintained on the node memory storage, the nodeprocessing unit is operative to perform steps from the exemplary methodsas described above. In more detail, the node processing unit isoperative to detect a signal from the ID node on the first communicationinterface as the ID node approaches the master node locatedsubstantially near a delivery point (such as a designated shippingarea), access the node memory storage to determine the shippinginformation related to the ID node and an intended recipient of the itembeing shipped from the shipping information, and instruct the secondcommunication interface to transmit a notification from the master nodeto the intended recipient where the notification informs or otherwisealerts the identified recipient about the item being substantially nearthe delivery point.

Related to determining shipping information, the node processing unitmay, in some embodiments, be further operative to determine anidentification of the ID node based upon the signal from the ID node,and determine the shipping information based upon the identification ofthe ID node. Related to transmitting the notification, the nodeprocessing unit may, in some embodiments, make use of an indirectnotification path and forward the notification to the server from themaster node with an instruction (implied or express) to cause the serverto send the notification to the intended recipient.

While FIGS. 34D and 41 describe an embodiment where the delivery pointusually remains in a fixed location, other embodiments may involve adelivery to a mobile delivery point, such as a vehicle (e.g., car, van,truck, train, ship/boat, aircraft, and the like). Delivery to such amoving or movable delivery point may find the responsible courier havingauthorized access to the movable delivery point, but may pose someadditional challenges given the location of the delivery point is notfixed. FIGS. 101A and 101B illustrate an example of another exemplarydelivery point stage in a shipping operation where an embodiment mayfacilitate the delivery and delivery notification for an item beingshipped to a mobile type of delivery point using a wireless nodenetwork. And while FIG. 102 illustrates an exemplary method of nodeoperations that helps facilitate delivery to the mobile delivery pointwith notification to an intended recipient, FIG. 103 illustrates anotherexemplary method of node operations that helps facilitate delivery tothe mobile delivery point with notification to an identified entityother than the intended recipient of the item being shipped.

In general and with reference to FIG. 101A, an exemplary mobile deliverypoint 10100 is shown associated with a mobile delivery point master node10110, which is operative to communicate with server 100. Package 130and related ID node 120 a are initially associated with a courier 10115having a courier master node 110 h (also operative to communicate withserver 100). In this embodiment, the delivery point 10100 may be mobile,such as a movable car or truck where the intended recipient desires tohave the package 130 placed within or otherwise delivered. Thus,embodiments of the mobile delivery point master node 10110 may beimplemented by a node on the vehicle (generally referenced as a vehiclenode), such as a master node, an ID node, a master node operating as anID node, or an ID node operating in a pseudo master node mode.

As the package 130 and ID node 120 a approach the mobile delivery point10100, mobile delivery point master node 10110 may detect advertisingsignals from ID node 120 a. Based on the signals, mobile delivery pointmaster node 10110 may determine shipping information related to theapproaching ID node 120 a and determine that courier master node 110 his currently associated with the ID node 120 a. Mobile delivery pointmaster node 10110 is then able to send location information (such as GPScoordinates or context data related to the mobile deliver point) tocourier master node 110 h as a way to assist and help guide the courier10115 responsible for the package 130 with delivery to the mobiledelivery point 10100. For example, mobile delivery point master node10110 may send courier master node 110 h location information on thevehicular mobile delivery point 10100, and that location information mayinclude GPS coordinates and/or context data, such as a vehicularidentification (e.g., Vehicle Identification Number or VIN, a licenseplate, an airplane tail number, or other tracking name or code affixedto the vehicle), a vehicular type (e.g., car, van, truck, privateairplane), a vehicular color, a vehicular make (e.g., Ford, GM, Lear,Cessna), a vehicular make (e.g., F-150 truck, Piper Cub airplane), aparking level or area (e.g., level 3 in a parking garage, a temporaryvisitor parking area), and a parking space number (e.g., space #13 inthe parking garage, hanger #44 at a private airport). In this manner,the vehicular node (mobile delivery point master node 10110) is contextaware and leverages this knowledge so as to help guide the courier tothe mobile delivery point with precise location information and/orcontextually relevant information that allows the courier to quickly andeasily identify the mobile delivery point and make the delivery.

When the ID node 120 a is substantially near the mobile delivery point10100 (more particularly, a storage area 10105 within vehicle 10100),the mobile delivery point master node 10110 may also notify the intendedrecipient of package 130 (via a message to smartphone 205). And as shownin FIG. 101B, the mobile delivery point master node 10110 may alsonotify the intended recipient and/or another entity (e.g., a shippingentity for the item, a business entity related to the mobile deliverypoint) when the ID node 120 a and package 130 have actually beendelivered to the mobile delivery point 10100. Thus, in some embodimentsas explained in more detail with respect to FIG. 103, deliverynotification may not necessarily require information on the intendedrecipient but may involve sending a notification upon delivery to theshipper and/or to a business that may own the mobile delivery point(e.g., a rental company that owns vehicle 10100).

In a further embodiment, delivery may be automatically acknowledged vianode signatures and reported by the mobile delivery point master node.For example, the ID node and the mobile delivery point master node maybecome associated as they approach each other and, once delivery isacknowledged through node interactions (e.g., passive or activeauthorized associations between the ID node with the item being shippedand the mobile delivery point master node that is authorized to receivethe item), the mobile delivery point master node may notify the serverabout the acknowledged delivery. In some embodiments, such nodeinteractions to acknowledge delivery may use security data (such assecurity data 335 implemented with cryptographic keys, PIN data, etc.)maintained by the ID node and the mobile delivery point master node intheir respective memories as discussed above relative to acknowledgeddeliveries and security data used when authorizing and authenticatingsuch transactions via node interactions.

In yet another embodiment, mobile delivery point master node 10100 maycontrol the authorized entry or access to storage area 10105 in oneembodiment via communication with courier master node 110 h or, inanother embodiment, by detecting ID node 120 a being proximate storagearea 10105. Locking elements (electronic door locks, electronic trunklocks or actuators) may be operated with signals from mobile deliverypoint master node 10100 to provide or control access within the mobiledelivery point 10100 (e.g., access to within storage area 10105 ofvehicle 10100). Such authorized access entry to storage area 10105 mayfurther involve verifying or validating access codes or keys provided bycourier master node 110 h or other security measures to ensure storagearea 10105 has limited access only by those authorized (e.g., courier10115) by the intended recipient. In another embodiment, an unlock keyset may be separately communicated to the courier master node 110 h(pre-staged or received upon coming close to the mobile delivery point.Other embodiments may use other types of keys as disclosed herein (e.g.,rotating type of key based on time, fixed type of key, pre-staged keyreceived when associating with the ID node and package initially, etc.).

FIG. 102 is a flow diagram illustrating an exemplary method for deliverynotification using a wireless node network in accordance with anotherembodiment of the invention. Referring now to FIG. 102, method 10200begins at step 10205 where the mobile delivery point master node detectsa signal from the ID node as the ID node approaches the mobile deliverypoint master node. Here, the mobile delivery point master node isrelated to a mobile delivery point (such as vehicle 10100) and the IDnode is related to an item being shipped (such as package 130). In moredetail, such a vehicle may be related to the intended recipient and maybe accessible by delivery personnel associated with the courier masternode, such as the courier having custody of package 130 and actuallydoing the delivering.

Method 10200 proceeds to step 10210 where the mobile delivery pointmaster node determines shipping information related to the ID node, anintended recipient of the item being shipped, and the courier masternode currently associated with the ID node. In a further embodiment ofmethod 10200, this determination may be accomplished after the mobiledelivery point master node determines an identification of the ID nodebased upon the detected signal from the ID node, and then determines theshipping information, the intended recipient, and the courier masternode based upon the identification of the ID node.

In still a further embodiment of method 10200, such a determination asperformed in step 10210 may be implemented with the mobile deliverypoint master node notifying the server that the mobile delivery pointmaster node and the ID node are associated; and then receivingresponsive information from the server about the shipping information,the intended recipient, and the courier master node currently associatedwith the ID node.

At step 10215, method 10200 has the mobile delivery point master nodetransmitting location information to the courier master node. Thelocation information comprises a current location of the mobile deliverypoint master node at the mobile delivery point. For example, mobiledelivery point master node 10110 shown in FIG. 101A may transmit amessage to courier master node 110 h (directly or via a relayed messageusing server 100). The message includes location information, such asthe current GPS coordinates, for mobile delivery point master node10110. As such, courier 10115 is made aware of where mobile deliverypoint 10100 is specifically located, which facilitates an easierdelivery as the ID node 120 a approaches the general area where mobiledelivery point 10100 is located.

In a further embodiment where the mobile delivery point is a vehicle,step 10215 may also have the mobile delivery point master nodetransmitting location information that may further comprise context datarelated to the vehicle. In other words, location information may includemore precise location data (e.g., GPS coordinates, altitude level, andthe like) and/or less precise types of location data, such as contextdata available to the mobile delivery point master node as contextuallyrelevant information that allows the courier to quickly and easilyidentify the mobile delivery point and make the delivery. Examples ofsuch relevant context data may include a vehicular identification (e.g.,Vehicle Identification Number or VIN, a license plate, an airplane tailnumber, or other tracking name or code affixed to the vehicle), avehicular type (e.g., car, van, truck, private airplane), a vehicularcolor, a vehicular make (e.g., Ford, GM, Lear, Cessna), a vehicularmodel (e.g., an F-150 truck from Ford Motor Company, a Cub airplane fromPiper Aircraft), a parking level or area (e.g., level 3 in a parkinggarage, a temporary visitor parking area), and a parking space number(e.g., space #13 in the parking garage, hanger #44 at a privateairport).

In another embodiment, method 10200 may include step 10220 where themobile delivery point master node instructs the ID node to alter an RFtransmission power level as the ID node approaches the mobile deliverypoint. This may be helpful in when the mobile delivery point is locatednear structure that may otherwise attenuate ID node transmissions orwhen the mobile delivery point is in a high node density environment.

At step 10225, method 10200 has the mobile delivery point master nodetransmitting a notification to the identified recipient in order toinform the intended recipient that the item being shipped issubstantially near the mobile delivery point. In other embodiments, thisnotification may occur when the item is within a threshold distance orreception range from the mobile delivery point master node. An advantagehere is that the intended recipient may be directly contacted by themobile delivery point master node without needing to then relay thenotification through the server, which may help offload the backendoperations and provide for quicker notifications.

However, in other embodiments, transmitting the notification maydesirably involve forwarding, by the mobile delivery point master node,the notification to the server, which then causes the server to send thenotification to the intended recipient. In more detail, notifying may beaccomplished by notifying the server that the mobile delivery pointmaster node has established a passive association with the ID nodewithout requiring an authorized connection between the mobile deliverypoint master node and ID node. Further still, another embodiment mayimplement notifying by notifying the server that the mobile deliverypoint master node has established an active association with the ID nodereflecting an authorized connection between the mobile delivery pointmaster node and ID node.

In a further embodiment, method 10200 may also include transmittingupdated location information by the mobile delivery point master node tothe courier master node. For example, if vehicle 10100 shown in FIG.101A moves, mobile delivery point master node 10110 may subsequentlytransmit its updated location via location information sent to couriermaster node 110 h. This may be done, for example, after the vehicle10100 moves a threshold distance from its prior reported location. Inanother example, this may be done periodically until the courierdelivers the package 130, as shown in FIG. 101B, to the vehicle 10100.

In still another embodiment, method 10200 may also have the mobiledelivery point master node transmit a warning notification to thecourier master node if the ID node is determined, by the mobile deliverypoint master node, to be moving away from the mobile delivery pointmaster node. In such a situation, the courier may be lost or, at least,is moving in a direction that appears to make delivery more difficult.The warning notification may allow the courier to alter its course andbe aware that it was moving away from the intended delivery of thepackage 130 to the mobile delivery point.

Once delivery has occurred, step 10230 of method 10200 has the mobiledelivery point master node transmitting a subsequent notification to theintended recipient about the item being delivered to the mobile deliverypoint. In more detail, the subsequent notification may inform theintended recipient that the item has been delivered to the mobiledelivery point. In a further embodiment, such a subsequent notificationmay also inform the intended recipient that the mobile deliver point(e.g., vehicle 10100) has be re-locked after the delivery so to allowthe recipient additional peace of mind with respect to the opted mobiledelivery point operation.

Those skilled in the art will appreciate that method 10200 as disclosedand explained above in various embodiments may be implemented on a node,such as an exemplary master node as illustrated in FIG. 4 or mobiledelivery point master node 10110 illustrated in FIGS. 101A and 101B,running one or more parts of a control and management code 425 toimplement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium, such as memorystorage 415 within an exemplary mobile delivery point master node. Thus,when executing such code, a processing unit 400 within the respectivemobile delivery point master node (as described below, for example) maybe operative to perform operations or steps from the exemplary methodsdisclosed above, including method 10200 and variations of that method.

From another perspective, another embodiment may include a mobiledelivery point master node for delivery notification involving a mobiledelivery point using a wireless node network having at least an ID node,a courier master node, and a server. The exemplary mobile delivery pointmaster node may comprise a node processing unit and a node memorystorage coupled to the node processing unit. The node memory storagemaintains code for execution by the node processing unit; shippinginformation related to an ID node and a related item being shipped; andidentification information related to the courier master node currentlyassociated with the ID node. The exemplary mobile delivery point masternode also comprises first and second communication interfaces each ofwhich being coupled to the node processing unit. The first communicationinterface being operative to communicate with the ID node while thesecond communication interface is operative to communicate with theserver.

When executing the code maintained on the node memory storage, the nodeprocessing unit of the mobile delivery point master node is adapted andoperative to perform steps from the exemplary methods as described aboverelative to method 10200. In more detail, the node processing unit isadapted and operative to detect a signal from the ID node via the firstcommunication interface as the ID node approaches the mobile deliverypoint master node, the mobile delivery point master node being relatedto the mobile delivery point (e.g., such as when a vehicle is the mobiledelivery point and the vehicle's master node operates as the mobiledelivery point master node), the ID node being related to an item beingshipped; access the node memory storage to determine the shippinginformation related to the ID node, an intended recipient of the itembeing shipped, and the courier master node currently associated with theID node; cause the location information to be transmitted to the couriermaster node, where the location information comprises a current locationof the mobile delivery point master node at the mobile delivery point;and instruct the second communication interface to transmit anotification from the mobile delivery point master node to theidentified recipient, where the notification informs the intendedrecipient about the item being substantially near the mobile deliverypoint or being actually delivered to the mobile delivery point.

As previously noted, while FIG. 102 illustrates an embodiment where anintended recipient may be notified related to delivery to a mobiledelivery point, FIG. 103 illustrates another exemplary method of nodeoperations that helps facilitate delivery to a mobile delivery point butwhere the notification may be sent to one or more entities other thanthe intended recipient of the item being shipped. As explained above, insome instances, pre-delivery and delivery confirmation notificationrelated to a mobile delivery point may not need to go to the ultimaterecipient of the item being shipped. For example, in one embodiment, amobile delivery point master node itself may acknowledge delivery with asecure signoff or handoff from the courier master node, and thedelivery-related notifications may go to one or more other entities,such as an entity identified in the shipping information.

Such an identified entity may be related to the mobile delivery point(e.g., a shipping company responsible for the overall logistics ofshipping the item to the mobile delivery point or a business entityrelated to the mobile delivery point, such as a rental car companyrelated to a rental car that is used as the mobile delivery point). Inthese examples, the mobile delivery point master node associated withthe mobile delivery point may send a notification to one of theseidentified entities that may or may not include the intended recipient.For example, a courier master node may deliver a package having an IDnode to a time-shared car, such as a Zipcar® automobile. The packagehere may, for example, include groceries or office supplies orderedonline. In this example, the Zipcar® automobile may be equipped with avehicle node that operates as a type of mobile delivery point masternode. As such, the node in the Zipcar® automobile may notify a shippingcompany responsible for delivering the package when the package issubstantially near that particular Zipcar® automobile and, for example,again after it has received the package and ID node to confirm deliveryto the shipping company and without the need to know the intendedrecipient. In some cases, the intended recipient may also be notified,if desired. In other cases, the Zipcar® business may be notified as abusiness entity related to the mobile delivery point via a messagedirectly to the business or via a message sent by the backend server. Instill further cases, multiple combinations of entities may be notifiedby the mobile delivery point master node (directly or indirectly via theserver) related to an impending and confirmed delivery of the package.

FIG. 103 is a flow diagram illustrating an exemplary method for deliverynotification using a wireless node network in accordance with anotherembodiment of the invention where notification is to an identifiedentity, which may be one or more entities other than the intendedrecipient of the packaged item being shipped. Referring now to FIG. 103,method 10300 begins at step 10305 where the mobile delivery point masternode detects a signal from the ID node as the ID node approaches themobile delivery point master node. Here, as with exemplary method 10200,the mobile delivery point master node in method 10300 is related to amobile delivery point (such as vehicle 10100) and the ID node is relatedto an item being shipped (such as package 130, which represents the itemand its packaging).

At step 10310, method 10300 has the mobile delivery point master nodedetermining shipping information related to the ID node and the couriermaster node currently associated with the ID node. In one embodiment,the shipping information related to the ID node and the courier masternode currently associated with the ID node may be pre-staged on themobile delivery point master node. As such, determining such informationmay be accomplished by accessing the information on the mobile deliverypoint master node's memory. However, those skilled in the art willappreciate that in another embodiment, the shipping information relatedto the ID node and which courier master node is currently associatedwith the ID node may be determined by requesting such information fromthe server 100. In more detail, step 10310 may further comprisenotifying the server that the mobile delivery point master node and theID node are associated, and receiving, by the mobile delivery pointmaster node, responsive information from the server about the shippinginformation and the courier master node currently associated with the IDnode.

At step 10315, the mobile delivery point master node transmits locationinformation to the courier master node currently associated with the IDnode. The location information includes a current location of the mobiledelivery point master node at the mobile delivery point. In an exampleembodiment where the mobile delivery point is a vehicle (such as thatshown in FIGS. 101A and 101B), step 10315 may also have the mobiledelivery point master node transmitting location information that mayfurther comprise information known to the mobile delivery point masternode about its contextual environment—i.e., context data related to thevehicle. In other words, various embodiments may have locationinformation including more precise types of location data (e.g., GPScoordinates, altitude level, and the like) and/or less precise types oflocation data, such as context data available to the mobile deliverypoint master node as contextually relevant information that allows thecourier to quickly and easily identify the mobile delivery point andmake the delivery. Examples of such context data may include a vehicularidentification (e.g., Vehicle Identification Number or VIN, a licenseplate, an airplane tail number, or other tracking name or code affixedto the vehicle), a vehicular type (e.g., car, van, truck, privateairplane), a color of the vehicle, a make or brand name of the vehicular(e.g., Ford, GM, Lear, Cessna), a model of the vehicle (e.g., an F-150truck from Ford Motor Company, a Caravan airplane from the CessnaAircraft Company), a parking level or area (e.g., level 3 in a parkinggarage, a temporary visitor parking area), and a parking space number(e.g., space #13 in the parking garage, hanger #44 at a privateairport).

At step 10320, the mobile delivery point master node may instruct the IDnode to alter an RF transmission power level as the ID node approachesthe mobile delivery point. As noted above with respect to method 10200,this may be helpful when the mobile delivery point is located nearstructure that may attenuate ID node transmissions or when the mobiledelivery point is in a high node density environment.

At step 10325, method 10300 has the mobile delivery point master nodetransmitting a notification to an entity identified in the shippinginformation. This informs the identified entity that the item issubstantially near the mobile delivery point. In other embodiments, thisnotification may occur when the item is within a threshold distance or acertain reception range from the mobile delivery point master node.

The entity notified is identified from the shipping information. Thismay allow the shipping customer to select and setup details on who orwhat is to be notified just before and upon delivery. As such, theidentified entity may not be the intended recipient of the shipped itemin the package 130. In a more detailed embodiment, the identified entitymay be an entity related to the mobile delivery point itself, such asone of a shipping entity for the item, a business entity related to themobile delivery point, and an intended recipient of the item or acombination thereof. In yet another embodiment where the mobile deliverypoint is a vehicle, the vehicle may be unrelated to the intendedrecipient but may be related to the business entity, and the vehicle maybe accessible by delivery personnel associated with the courier masternode. In still another embodiment, the vehicle may be unrelated to theintended recipient at the time of delivery only later to become relatedto the intended recipient (e.g., delivery to a specific rental car priorand then later assigning that specific rental car to the intendedrecipient).

In other embodiments, transmitting the notification to the identifiedentity may take a less direct approach in that it may desirably involveforwarding the notification to the server by the mobile delivery pointmaster node. This then causes the server to send the notification to theidentified entity. In more detail, notifying may be accomplished bynotifying the server that the mobile delivery point master node hasestablished a passive association with the ID node without requiring anauthorized connection between the mobile delivery point master node andID node. Further still, another embodiment may implement notifying bynotifying the server that the mobile delivery point master node hasestablished an active association with the ID node reflecting anauthorized connection between the mobile delivery point master node andID node.

In a further embodiment, method 10300 may also include transmittingupdated location information by the mobile delivery point master node tothe courier master node. For example, if vehicle 10100 shown in FIG.101A moves, mobile delivery point master node 10110 may subsequentlytransmit its updated location via location information sent to couriermaster node 110 h. This may be done, for example, after the vehicle10100 moves a threshold distance from its prior reported location. Inanother example, this may be done periodically until the courierdelivers the package 130, as shown in FIG. 101B, to the vehicle 10100.

In still another embodiment, method 10300 may also have the mobiledelivery point master node transmit a warning notification to thecourier master node if the ID node is determined, by the mobile deliverypoint master node, to be moving away from the mobile delivery pointmaster node. In such a situation, the courier may be lost or, at least,is moving in a direction that appears to make delivery more difficult.The warning notification may allow the courier to alter its course andbe aware that it was moving away from the intended delivery of thepackage 130 to the mobile delivery point.

Once delivery has occurred, step 10330 of method 10300 may have themobile delivery point master node transmitting a subsequent notificationto the identified entity about the item being delivered to the mobiledelivery point. In more detail, the subsequent notification may informthe identified entity that the item has been delivered to the mobiledelivery point. In a further embodiment, such a subsequent notificationmay also inform the identified entity that the mobile deliver point(e.g., vehicle 10100) has been re-locked after the delivery.

Those skilled in the art will appreciate that method 10300 as disclosedand explained above in various embodiments may be implemented on a node,such as an exemplary master node as illustrated in FIG. 4 or mobiledelivery point master node 10110 illustrated in FIGS. 101A and 101B,running one or more parts of a control and management code 425 toimplement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium, such as memorystorage 415 within an exemplary mobile delivery point master node. Thus,when executing such code, a processing unit 400 within the respectivemobile delivery point master node may be operative to perform operationsor steps from the exemplary methods disclosed above, including method10300 and variations of that method as described above.

In another perspective, another embodiment may include a mobile deliverypoint master node for delivery notification using a wireless nodenetwork having at least an ID node, a courier master node, and a server.The exemplary mobile delivery point master node may comprise a nodeprocessing unit and a node memory storage coupled to the node processingunit. The node memory storage maintains code for execution by the nodeprocessing unit (such as one or more parts of the control and managementcode 425); shipping information related to an ID node and a related itembeing shipped; and identification information related to the couriermaster node currently associated with the ID node. The exemplary mobiledelivery point master node also comprises first and second communicationinterfaces each of which being coupled to the node processing unit. Thefirst communication interface is operative to communicate with the IDnode while the second communication interface is operative tocommunicate with the server.

When executing the code maintained on the node memory storage, the nodeprocessing unit of the mobile delivery point master node is adapted andoperative to perform steps from the exemplary methods as described aboverelative to method 10300 and its variations as described above. In moredetail, the node processing unit is adapted and operative (via executionof the code) to detect a signal from the ID node via the firstcommunication interface as the ID node approaches the mobile deliverypoint master node (where the mobile delivery point master node isrelated to a mobile delivery point and the ID node is related to an itembeing shipped); access the node memory storage to determine the shippinginformation related to the ID node and the courier master node currentlyassociated with the ID node; cause the location information to betransmitted to the courier master node (where the location informationcomprises a current location of the mobile delivery point master node atthe mobile delivery point); and instruct the second communicationinterface to transmit a notification to an entity identified in theshipping information, where the notification informs the identifiedentity about the item being substantially near or being actuallydelivered to the mobile delivery point.

Order Pickup Using a Wireless Node Network

In another embodiment, picking up an order placed with a retail facilitymay be advantageously facilitated using a master node and a mobile useraccess device operating as an advertising ID node within a wireless nodenetwork. A retail order may generally be an item purchased that may bepicked up from a facility. In a more detailed example, a customersubmits an order to a retail establishment, such as a FedEx® OfficePrint & Ship Center, for an item. In one example, the ordered item mayinclude a number of specifically printed documents bound together in adesired way (e.g., spiral bound with distinct covers). The exemplaryorder may be submitted by the customer in person at the retailestablishment (more generally referred to as a facility). In anotherexample, the order may be submitted online to the retail establishmentby the customer via a website where the customer may have an account orprofile. Such an account or profile may identify the customer andidentify and register a mobile user access device that may be used whenpicking up the order. In both the in-person and online order submissionpaths for an exemplary order, an order management system for the retailestablishment may receive information about the order (e.g., anidentification of the customer, specific information on what items wereordered, an identification of a mobile user access device to be usedwhen picking up the order, etc.) and help to fulfill the order for thecustomer.

FIG. 42 is a diagram illustrating an example environment for picking upan order using exemplary components of a wireless node network inaccordance with an embodiment of the invention. Referring now to FIG.42, an exemplary order management system 4205 is illustrated that mayhave received the order and is generally responsible for the order andits fulfillment. Those skilled in the art will appreciate that ordermanagement system 4205 may be implemented by a wide variety ofcomputer-based systems, such as server-type sales management systemsinvolved in online sales management, order fulfillment, and order statusreporting.

In the illustrated example, exemplary order management system 4205 isrelated to facility 4200 where the order 4210 is to be picked up. Thefacility 4200 also has a related office master node 4215 deployed at ornear a designated order fulfillment area 4220 (more generally a pickuppoint) where a previously submitted order for one or more items are madeavailable to customers. In one example, the order may be a print ordergenerated by a printer. In another example, the order may be a 3D printorder generated by a 3D printer. In further examples, the order may beother retail items.

In one example, the office master node 4215 may be at or substantiallynear a customer pickup counter (a more specific pickup point). Officemaster node 4215 is operative to communicate with server 100 as part ofthe wireless node network. Server 100 may be separate from ordermanagement system 4205 in one embodiment, but server 100 may alsofunction as the order management system 4205 in other embodimentsdepending on how the retail establishment elects to deploy its servercomputing resources.

As shown in FIG. 42, a mobile user access device 200 registered to pickup the order approaches the facility 4200. An exemplary mobile useraccess device may be implemented in a wide variety of forms, such as alaptop computer, a tablet device, a personal area network device, asmartphone device, and a smart wearable device. Furthermore, thoseskilled in the art will appreciate that code operative on the exemplarymobile user access device 200 (e.g., an app on a smartphone) may be usedalong with the conventional features of the mobile user access device tocommunicate over a short-range communication path, such as a Bluetooth®Low Energy enabled RF communication path, and allow the mobile useraccess device to operate as an advertising ID node as described herein.In other words, the mobile user access device 200 may operate as anadvertising ID node when it approaches the facility 4200 in anembodiment in order to facilitate pickup of the order. As the mobileuser access device 200 approaches and when the office master node 4215detects a signal from the mobile user access device 200 operating as anadvertising ID node, the office master node 4215 associates with themobile user access device 200.

The office master node 4215, having an identification of the mobile useraccess device 200 being registered to the order, may notify the ordermanagement system 4205 upon detecting such a signal from the mobile useraccess device 200. In another embodiment, office master node 4215 maywait for such notification, and continue to determine the location ofthe mobile user access device 200 operating as an advertising ID node asthe device 200 keeps approaching the master node, and notify the ordermanagement system 4205 when the device 200 is within a predeterminedrange of the pickup point in facility 4200. Thus, office master node4215 and device 200 operating as an ID node may allow for a proactivenotification of and integration into the order management system 4205 sothat the order 4210 may be ready by the time device 200 (and thecustomer carrying device 200) arrive at the pickup point.

FIG. 43 is a flow diagram illustrating an exemplary method pickup of anorder using a wireless node network in accordance with an embodiment ofthe invention. Referring now to FIG. 43, exemplary method 4300 begins atstep 4305 where a master node associated with a pickup point receivesorder information from a server. The order information provides anidentification of the order and an identification of a mobile useraccess device registered for the pickup of the order. The pickup point,in one embodiment, may be a designated location where the order will beavailable, such as an order fulfillment area in a facility, a pickupdesk or counter within a retail establishment, or the like.

At step 4310, detecting, by the master node, a signal broadcast from themobile user access device identified by the order information when themobile user access device is operating as an advertising ID node in thenetwork and as the mobile user access device approaches the master node.In one embodiment, master node may be able to detect the signal is fromthe particular mobile user access device registered with the orderbecause the identification of the mobile user access device may appearin header information of the signal broadcast from the mobile useraccess device when operating as the advertising ID node. For example,smartphone 200 illustrated in FIG. 42 may be operating as an ID node byadvertising or broadcasting a signal (such as an advertisement packetsimilar to that shown in FIG. 7) formatted with header information thatidentifies a Bluetooth® Low Energy (BLE) signature (e.g., a MAC addressor other header information) related for this particular smartphone 200.Thus, in this example, the exemplary app (not shown) resident onsmartphone 200 is able to control such BLE signals emitted and read BLEsignals received to operatively enable smartphone 200 to function as anadvertising ID node.

At step 4315, method 4300 continues by associating the master node andthe identified mobile user access device operating as the advertising IDnode. The association may be passive or active depending on a desire tosecurely share information with the mobile user access device. Thus, inone embodiment, the associating at step 4315 may further compriseestablishing a passive association between the master node and theidentified mobile user access device operating as the advertising IDnode without requiring an authorized connection between the master nodeand the identified mobile user access device operating as theadvertising ID node. However, in another embodiment, such associatingmay further comprise establishing an active association between themaster node and the identified mobile user access device operating asthe advertising ID node reflecting an authorized connection between themaster node and the identified mobile user access device operating asthe advertising ID node. In more detail, establishing an activeassociation may involve the master node determining when the identifiedmobile user access device operating as the advertising ID node isconnectable, requesting authorization from the server to associate withthe identified mobile user access device operating as the advertising IDnode, and receiving the requested authorization from the server to allowthe authorized connection between the master node and the identifiedmobile user access device operating as the advertising ID node.

At step 4320, the master node notifies an order management systemresponsible for the order (such as order management system 4205 shown inthe example of FIG. 42). This notification occurs when the master nodedetermines a location of the identified mobile user access deviceoperating as the advertising ID node to be within a predetermined rangeof the pickup point. In another embodiment where the master node, thenotifying step may comprise transmitting a message from the master nodeto the server, where the message causes the server to notify the ordermanagement system that the identified mobile user device related to theorder is approaching the pickup point to receive the order.

Method 4300 may further include steps that provide feedback to themobile user access device prior to pick up. In more detail, such stepsmay include the master node receiving an order update message from theorder management system where the order update message reflects a statusof the order. For example, if the order is not yet ready for pickup, themaster node may inform the customer by transmitting a pickup statusmessage to the identified mobile user access device operating as theadvertising ID node. However, if the order is ready for pickup or ifthere is other status information to convey to the designated pickupdevice, the pickup status message provides a proactive way of doing so.

In a further embodiment, the pickup status message may cause theidentified mobile user access device operating as the advertising IDnode to display one or more prompts (e.g., prompted messages) on a userinterface of the identified mobile user access device. For example, theprompt may be related to picking up the order, validating that the orderhas been picked up, and/or paying for the order.

Those skilled in the art will appreciate that method 4300 as disclosedand explained above in various embodiments may be implemented on amaster node, such as an exemplary master node as illustrated in FIG. 4or office master node 4215 illustrated in FIG. 42, running one or moreparts of a control and management code 425 to implement any of the abovedescribed functionality. Such code may be stored on a non-transitorycomputer-readable medium, such as memory storage 415 within an exemplarymaster node. Thus, when executing such code, a processing unit 400within the respective master node may be operative to perform operationsor steps from the exemplary methods disclosed above, including method4300 and variations of that method.

In another embodiment, an exemplary master node for pickup of an orderat a pickup point using a wireless node network comprises a nodeprocessing unit at its core. The master node also comprising a nodememory storage, a first communication interface, and a secondcommunication interface—each of which being coupled to the nodeprocessing unit. The node memory storage maintains code for execution bythe node processing unit (such as control and management code 425) andorder information having an identification of the order and anidentification of the mobile user access device registered to pick upthe order. For example, the order may be a print order submitted by acustomer having an account or profile information with a FedEx a FedEx®Office Print & Ship Center that is associated with the order. Thus, thecustomer may have registered one or more mobile user access devices onthe account or profile. As a result, such registered mobile user accessdevice or devices may be considered identified or registered to pick upthe order even though the customer need only use one of the registereddevices when picking up the order.

In the master unit, the first communication interface coupled to thenode processing unit is operative to communicate with the mobile useraccess device operating as an advertising ID node over a short-rangecommunication path, such as over a Bluetooth® Low Energy formattedsignal communication path. Instead of using this short-rangecommunication path, the second communication interface of the masternode is coupled to the node processing unit and operative to communicatewith the server. In one example, the communication path for the masternode to communicate with the server is a wireless higher-speed,longer-range communication path when compared to the short-rangecommunication path of the first communication interface.

The node processing unit, when executing the code maintained on the nodememory storage, is operative to perform steps substantially similar tothose described above with respect to method 4300. More specifically,the node processing unit is operative to receive the order informationfrom the server and maintain the order information on the node memorystorage, and receive a signal detected by the first communicationinterface and broadcast from the mobile user access device when themobile user access device is operating as an advertising ID node in thenetwork and approaching the first communication interface. The nodeprocessing unit may be operative, in a more detailed embodiment, todetermine if the signal detected by the first communication interface isfrom the identified mobile user access device by analyzing headerinformation of the signal broadcast from the mobile user access deviceoperating as the advertising ID node

The node processing unit is further operative to associate the masternode and the identified mobile user access device operating as theadvertising ID node. In one embodiment, the node processing unit mayassociate the master node and the identified mobile user access deviceoperating as the advertising ID node by being further operative toestablish a passive association between the master node and theidentified mobile user access device operating as the advertising IDnode without requiring an authorized connection over the firstcommunication interface between the master node and the identifiedmobile user access device operating as the advertising ID node. Inanother embodiment, the node processing unit may associate the masternode and the identified mobile user access device operating as theadvertising ID node by being further operative to establish an activeassociation between the master node and the identified mobile useraccess device operating as the advertising ID node reflecting anauthorized connection over the first communication interface between themaster node and the identified mobile user access device operating asthe advertising ID node. The node processing unit may, in even moredetail, be operative to establish the active association by beingfurther operative to (1) determine when the identified mobile useraccess device operating as the advertising ID node is connectable, (2)transmit an authorization request over the second communicationinterface to the server, and (3) receive an authorization response fromthe server over the second communication interface to allow theauthorized connection between the master node and the identified mobileuser access device operating as the advertising ID node. As such, theauthorized connection may use the first communication interface to shareinformation between the master node and the mobile user access device.

The node processing unit is operative to determine if a location of theidentified mobile user access device operating as the advertising IDnode is within a predetermined range of the pickup point. When themessage being transmitted when the identified mobile user access deviceoperating as the advertising ID node is determined to be within apredetermined range of the pickup point, the node processing unit isstill further operative to transmit a message over the secondcommunication interface to notify an order management system responsiblefor the order.

In another embodiment of the master node, the node processing unit maytransmit the message over the second communication interface to notifythe order management system by being further operative to transmit anintermediate message to the server to cause the server to notify theorder management system that the identified mobile user device relatedto the order is approaching the pickup point to receive the order.

In still another embodiment, the node processing unit may be furtheroperative to receive an order update message from the order managementsystem over the second communication interface where the order updatemessage reflects a status of the order. And the node processing unit mayalso be operative to transmit a pickup status message to the identifiedmobile user access device operating as the advertising ID node over thefirst communication interface, where the pickup status message informsthe identified mobile user access device of the status of the order.

Managing Delivery Using Node Signatures

As described in several of the embodiments, a signal broadcast oradvertised by an exemplary node in a wireless node network provides atype of signature for the node. This signature may be detected andapplied in a variety of embodiments to facilitate, for example, animproved or enhanced logistics process involving package delivery andpayment on delivery (also referred to as cost on delivery or COD). Theexample illustrated in FIG. 34D was previously discussed in terms ofdelivery notification as package 130 and ID node 120 a approached masternode 3445 associated with delivery point 3440. However, managingdelivery to the intended recipient (such as a customer using mobile useraccess device 205) may be further enhanced in an embodiment as describedin more detail below when the recipient's mobile user access device 205operates as a master node that detects the ID node 120 a related topackage 130 as device 205 gets close enough to ID node 120 a.

Notably, FIG. 34D illustrates an embodiment where master node 3445 is incommunication with server 100. As explained with reference to FIG. 41,the intended recipient may be notified of delivery of package 130 andrelated ID node 120 a when the ID node 120 approaches a delivery point3440 (such as a shipping area, loading dock, mail room, and the like).However, after mobile user access device 205 may be notified that thepackaged item (and its related ID node 120 a) is substantially neardelivery point 3440, the intended recipient using mobile user accessdevice 205 may approach the package 130 and ID node 120 a as part of thedelivery.

In this example, mobile user access device 205 may be functioning as anexemplary master node with a short-range communication path to ID node120 a and with a longer-range communication path to server 100. Aspreviously explained above, an embodiment of device 205 may beimplemented as a mobile user access device (such as a smartphone) andmay operate as an exemplary master node (such as master node 110 a ofFIG. 4) that communicates and associates with other nodes (e.g., IDnodes and other master nodes) as described herein, and communicates withthe server 100. In more detail, this may be accomplished with theprocessor in the user access device, peripheral circuitry coupled to theprocessor, and an app or other code executing in mobile user accessdevice 205 as master control and management code 425 along with relevantmaster node related data (as explained in more detail in FIG. 4). Theexemplary app or program module implementing master control andmanagement code 425 on device 205 may leverage, for example, use of anexisting Bluetooth® Low Energy (BLE) communication capability of thedevice 205 (e.g., a type of short range communication interface 480 foran exemplary master node 110 a) in a format and manner as describedherein as a master node (e.g., as explained in FIGS. 6-12). This allowsdevice 205 to advertise signals having exemplary packet messages asshort-range signals and associate (passively or actively in anauthorized manner) with other nodes in the network (such as master node3445 or ID node 120 a).

Those skilled in the art will appreciate that the described embodimentsof managing delivery of an item being shipped using elements of awireless node network (such as an ID node related to the item beingshipped, a mobile user access device operative to function as a masternode, and a server) fundamentally effect an improvement in how shippeditems may be tracked as part of an improved type of logisticstechnology. Such an enhanced ability to manage delivery of a shippeditem that leverages elements of the wireless node network improvestechnical fields such as logistics, shipping management, inventorymanagement, and the like. In other words, the exemplary embodimentsdescribed herein with interrelated operations between elements of awireless node network to manage a delivery of a shipped item provide atype of specially-adapted system that enhances and improves operationsin technical fields such as logistics, shipping management, retailinventory management, and the like.

FIG. 44 is a flow diagram illustrating an exemplary method for managinga delivery of an item being shipped using a wireless node network inaccordance with an embodiment of the invention. Referring now to FIG.44, method 4400 begins at step 4405 where the mobile user access deviceoperative to function as the master node receives shipping informationfrom the server. The shipping information is related to the item beingshipped and includes an identification of the ID node related to theitem being shipped. In the example of FIG. 34D, the exemplary shippinginformation is related to the item within package 130 and includes anidentification of ID node 120 a related to the item being shipped.

At step 4410, the mobile user access device operative to function as themaster node detects a signal broadcast from the ID node as the ID nodecomes within a communication range of the mobile user access deviceoperative to function as the master node. In one example, the signal isan advertising packet message transmitted from ID node 120 a.

At step 4415, the method associates the ID node and the mobile useraccess device operating as the master node to acknowledge the deliveryof the item and, at step 4420, the mobile user access device operatingas the master node notifies the server with a notification about theacknowledged delivery.

In one embodiment, associating may comprise establishing a preauthorizedconnection between the ID node and the mobile user access deviceoperating as the master node to acknowledge the delivery of the item. Inmore detail, establishing the preauthorized connection may be based upona previously authorized acceptance condition that occurs automaticallywhen the mobile user access device operating as the master node detectsthe signal broadcast as an advertising signal from the ID node. Thus, inone embodiment, the preauthorized connection may be automaticallyestablished (without the need for an prompted acknowledgement) as soonas the ID node's advertising signal is detected by the mobile useraccess device operating as the master node. However, in anotherembodiment, the preauthorized connection may be automaticallyestablished when the mobile user access device operating as the masternode is located within a threshold distance from the ID node. The mobileuser access device operating as the master node (device 205 in FIG. 34D)may periodically determine the location of ID node 120 a relative to itsown location as part of establishing the preauthorized connection.

In another embodiment, associating may comprise establishing apreauthorized connection between the ID node and the mobile user accessdevice operating as the master node to acknowledge the delivery of theitem for automatic payment on delivery purposes. In this embodiment, themethod may also notify the server by the mobile user access deviceoperating as the master node with a notification indicating thesuccessfully established preauthorized connection. The mobile useraccess device operating as the master node may also instruct the serverto complete a payment transaction related to the item being shipped at arate charged lower than if an active prompted connection was establishedfor payment on delivery purposes between the ID node and the mobile useraccess device operating as the master node. Thus, a COD customer may beable to create an acceptance condition (e.g., when the customer's mobileuser access device operating as a master node receives a signal from theID node related to the packaged item being shipped) that preauthorizes aconnection and allows for a payment transaction for the item to becompleted without some other kind acknowledgement or active feedbackfrom the COD customer.

In another embodiment, associating may comprise establishing an activeprompted connection between the ID node and the mobile user accessdevice operating as the master node to acknowledge the delivery of theitem after receiving a prompted acknowledgment of the delivery of theitem. For example, rather than an automatic connection upon detectingthe ID node's advertising signal, an active acknowledgement from thecustomer that ordered the item is needed to acknowledge delivery of theitem.

In still another embodiment, associating may comprise establishing anactive prompted connection for payment on delivery purposes between theID node and the mobile user access device operating as the master node.And, as such, method may further include notifying the server by themobile user access device operating as the master node. Here, thenotification may indicate a successfully established active promptedconnection for payment on delivery purposes and instruct the server tocomplete a payment transaction related to the item being shipped.

Those skilled in the art will appreciate that method 4400 as disclosedand explained above in various embodiments may be implemented on a node,such as an exemplary master node as illustrated in FIG. 4 andimplemented as a type of mobile user access device, running one or moreparts of a control and management code 425 to implement any of the abovedescribed functionality. Such code may be stored on a non-transitorycomputer-readable medium, such as memory storage 415 within an exemplarymaster node. Thus, when executing such code, a processing unit 400within the respective master node may be operative to perform operationsor steps from the exemplary methods disclosed above, including method4400 and variations of that method.

In another embodiment, a system for managing a delivery of an item beingshipped using a wireless node network may be used to perform similarsteps. In more detail, the system comprises a server and a master nodein communication with the server. The master node comprises a nodeprocessing unit and a node memory coupled to the node processing unit.The node memory maintaining code for execution by the node processingunit and shipping information related to the item being shipped. Theshipping information comprises an identification of an ID node relatedto the item being shipped. With this information, the node processingunit is operative, when executing the code, to receive the shippinginformation from the server and maintain the shipping information on thenode memory, and receive a signal detected by the first communicationinterface and broadcast from the ID node. The signal is detected as theID node comes within a communication range of the first communicationinterface. The node processing unit is further operative to associatethe ID node and the master node to acknowledge the delivery of the item,and transmit a message over the second communication interface to notifythe server about the acknowledged delivery.

In a particular embodiment, the master node comprises a mobile useraccess device, such as a laptop computer, a tablet device, a personalarea network device, a smartphone device, and a smart wearable device.More specifically, the master node is a mobile user access deviceoperating as a master node.

In several different embodiments, the node processing unit is operativeto associate the ID node and the master node in particular ways. In oneexample, the node processing unit may associate the ID node and themaster node by being further operative to establish a preauthorizedconnection between the ID node and the master node to acknowledge thedelivery of the item. In another example, the node processing unit mayassociate the ID node and the master node by being further operative toestablish a preauthorized connection between the ID node and the masternode to acknowledge the delivery of the item for automatic payment ondelivery purposes. In still another example, the node processing unitmay associate the ID node and the master node by being further operativeto establish an active prompted connection between the ID node and themaster node to acknowledge the delivery of the item after the masternode receives input from a user of the master node, the input being aprompted acknowledgment of the delivery of the item. And in yet anotherexample, the node processing unit may associate the ID node and themaster node by being further operative to establish an active promptedconnection for payment on delivery purposes between the ID node and themaster node.

In still another embodiment, the node processing unit may be furtheroperative to notify the server over the second communication interfacewhere the notification indicates a successfully established activeprompted connection for payment on delivery purposes. The notificationmay also instruct the server to complete a payment transaction relatedto the item being shipped.

Multi-Entity Management of Location Services

A node, for example an ID node, may have multiple distinct users (ormore generally entities) each with a possible desire to independentlyadminister the node and access its collected data. In such a situation,exemplary methods for managing hand-off and custodial chain of the nodeand its data may be helpful.

In the example shown in FIG. 17, for instance, essentially threeentities are illustrated as managing ID node 120 a—e.g., a sender as afirst entity that operates user access device 200 during the preparationphase 1700, a shipping entity (e.g., FedEx) that operates or is relatedto various master nodes during the shipment or transit phase 1705, and arecipient as a third entity that operates user access device 205 duringthe possession phase 1710.

In a general embodiment, ID node 120 a may start in possession of thesender, as shown in FIG. 17 during the preparation phase 1700. In thisexample, the sender's (shipping customer's) user access device 200(e.g., a smartphone) also functions as a master node through at leastone program module of code (e.g., an app, an application, or severalinteracting program modules operating as code 425) running on theirdevice. This master node code communicates with the backend server 100,which has server-side software to help manage master-to-ID nodeassociations (as discussed above regarding the server-side associationmanager program module in exemplary code 525).

In one example, the ID node 120 a may have been associated with themaster node (user access device 200) previously by a request issued fromthe sender's device 200 to the server 100 (via network 105) resulting inauthorized access. This may give the holder of that authorizationcertain rights to the data to be collected and management of the ID node120 a. As will be explained in more detail below, exemplaryauthorizations provided by server 100 may include certain privilegesthat authorize such rights under particular circumstances and forparticular types of information (e.g., paid for privileges, limitedaccess privileges, access to data collected, access to locationinformation, privileges to track an item associated with the ID nodeover time, etc.).

When the sender initiates shipment with a shipping entity, such asFedEx, and associates the ID node 120 a with the shipment data, theinitially granted privilege is transferred back to the shipping entitythrough the server 100, which instructs a likely first master node inthe shipping entity's network to see the package 130 having ID node 120a to accept advertising messages from ID node 120 a. For example, themaster node may be part of a drop box (e.g., drop node 110 a), a lockersystem and/or a handheld courier device (e.g., courier node 110 b). Whensuch a master node reports seeing the package 130 (e.g., by detecting anadvertising signal from ID node 120 a), the prior privilege for thesender's device 200 to directly access the ID node 120 a is terminated.Active access to ID node 120 a at that point remains limited to theshipping entity until the package is delivered to the recipient. Whendelivered to the recipient, their user access device 205 (e.g., anothersmartphone), running the master node software (such as code 425), canissue a request to the server 100 asking to take over control of the IDnode. If the server grants the request to have such destinationprivileges based on particular conditions (e.g., payment, limited scopeof control or access to data, etc.), the data associated with the IDnode 120 a after the transition of ownership is made available to the tothe recipient user access device 205. If not granted, the data ownershipand management for ID node 120 a remains with the shipping entity.

In another embodiment, when an ID node is associated with an entityoutside of the shipping entity (e.g., with the sender's user accessdevice 200 or the recipient's user access device 205), the applicationon their device would allow for management of where the collected datashould be stored. For example, the collected data in the ID node mayonly be visible to the entity outside of the shipping entity (via theirmaster node operating device) and not uploaded to the server 100 unlessdirected to do so and allowed by server 100. Hosting of this data may bepart of a service offered to the user by shipping entity that operatesand manages server 100. Regardless of where data is held, for managementfunctions, the ID node may still periodically communicate to the server100 to check for updates of software and instructions.

FIGS. 64-66 are flow diagrams illustrating exemplary methods formulti-entity management of an ID node from various operationalperspectives. In more detail, FIG. 64 is a flow diagram illustrating anexemplary method for multi-entity management of an ID node in a wirelessnode network in accordance with an embodiment of the invention from theperspective of exemplary ID node operations. Referring now to FIG. 64,method 6400 begins at step 6450 by associating the ID node with a firstentity user access device. The first entity user access device isoperating as a master node in the network (such as the previouslydescribed sender's device 200 operating as a master node). As such amaster node, the first entity user access device is operative tocommunicate directly with a server in the network over a first (e.g.,longer range) communication path and separately communicate with the IDnode over a second (e.g., shorter range) communication path. And the IDnode is operative to communicate directly with the first entity useraccess device over the second communication path but is unable todirectly communicate with the server.

At step 6410, the ID node provides the associated first entity useraccess device with access to data collected by the ID node if authorizedby an initial privilege, which was provided by the server to the firstentity user access device. In one embodiment, the initial privilege maycomprise a paid privilege to access the data collected by the ID node.For example, the sender may pay when obtaining ID node 120 a to be ableto access information related to the node as the node is used. Inanother embodiment, the initial privilege may comprise a paid privilegeto be provided a location of the ID node. So for example, the sender maypay for a specific type of information, such as to be informed of thecurrent location of the ID node 120 a or the package 130 with the IDnode 120 a. In a further embodiment, the initial privilege may comprisea paid privilege to track an item associated with the ID node over time.And in the same example, the sender may pay for an even more specificservice related to the data gathered and collected—namely, for atracking service for the item packaged in package 130 related to ID node120 a.

Other options may allow the sender to customize how they want to storeor maintain data collected by the ID node. In one embodiment, theinitial privilege may comprise a privilege for the first entity useraccess device to manage where the data collected by the ID node isstored. In more detail, the initial privilege may comprise a paidprivilege to have the data collected by the ID node uploaded to thefirst entity user access device over the second communication path.Thus, the data may be shared with the device operating as a master node.In a further embodiment, the initial privilege may comprise a paidprivilege to have the data collected by the ID node also uploaded to theserver from the first entity user access device over the firstcommunication path.

At step 6415, the ID node is associated with a shipping entity masternode in the network. For example, as shown in FIG. 17, ID node 120 a maybe associated with drop node 110 a (a type of master node operated by ashipping entity, such as FedEx). While method 6400 includes the ID nodechanging custodial control to only one shipping entity master node,those skilled in the art will appreciate with reference to FIG. 17 thatcustodial control and handoff of ID node 120 a may happen with severaldifferent shipping entity master nodes (e.g., courier node 110 b,vehicle node 110 c, facility node 110 d, ULD node 110 e, facility node110 f, delivery vehicle node 110 g, and courier node 110 h) beforehandoff to the recipient may occur for delivery.

At step 6420, the ID node provides the associated shipping entity masternode with access to the data collected by the ID node based upon atransferred privilege, which is provided by the server to the shippingentity master node.

At step 6425, the ID node is associated with a second entity user accessdevice. In another embodiment, method 6400 may have the ID noderestricting the first entity user access device from directly accessingthe data collected by the ID node after the ID node is associated withthe shipping entity master node.

At step 6430, the ID node provides the associated second entity useraccess device with access to the data collected by the ID node ifauthorized by a destination privilege provided by the server to thesecond entity user access device. In one embodiment, the destinationprivilege may comprise a paid privilege to access any of the datacollected by the ID node. In another embodiment, the destinationprivilege may comprise a paid privilege to access only a limited portionof the data connected by the ID node. For example, some of the datacollected may not be of interest to the consumer, but some may beinteresting and valued enough to cause a consumer to pay for even thelimited portion of the data (e.g., specific types of data, only limitedor periodic samples of certain data, only a summary of the data, etc.).

In a further embodiment, the data collected by the ID node while the IDnode is associated with the shipping entity master may remain owned bythe shipping entity related to the shipping entity master node when thesecond entity user access device is not authorized by the destinationprivilege. Thus, if rights to such data are not granted, the shippingentity may maintain ownership of the data and control of the ID node.

And in another embodiment, method 6400 may allow the ID node to requestsystem updates (e.g., software updates for any code on the ID node) fromthe server by the ID node regardless of where the data collected by theID node is stored.

Those skilled in the art will appreciate that method 6400 as disclosedand explained above in various embodiments may be implemented on an IDnode (such as exemplary ID 120 a as illustrated in FIGS. 3 and 17),running one or more parts of a control and management code (such as code325) to implement any of the above described functionality. Such codemay be stored on a non-transitory computer-readable medium (such asmemory storage 315 in an exemplary ID node). Thus, when executing suchcode, a processing unit of the ID node (such as unit 300) may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 6400 and variations of that method.

FIG. 65 is a flow diagram illustrating an exemplary method formulti-entity management of an ID node in a wireless node network fromthe perspective of a shipping customer entity in accordance with anembodiment of the invention. Referring now to FIG. 65, method 6500begins at step 6505 by executing a program module of code (such asmaster node control and management code 425) on a first entity useraccess device to enable operation of the first entity user access deviceas a master node. As such, the first entity user access device isoperative to communicate directly with a server over a firstcommunication path (as a master node) and separately communicate withthe ID node over a second communication path (as a master node). And theID node is operative to communicate directly with the first entity useraccess device over the second communication path but unable to directlycommunicate with the server.

At step 6510, method 6500 continues by transmitting a request to theserver from the first entity user access device. The request is for anauthorization to associate with the ID node and to provide an initialprivilege related to data to be collected by the ID node. In oneembodiment, the authorization and the initial privilege are separatedata items, however in other items both are implemented as part of theauthorization (e.g., the initial privilege may be at least oneauthorized task or privilege approved by the server to be performedbetween the master node and the ID node).

In one embodiment, the initial privilege may comprise a paid privilegeor, in more detail, a paid privilege for access to the data collected bythe ID node. Method 6500 may also include receiving, by the first entityuser access device, a location of the ID node if authorized by theinitial privilege. And method 6500 may further include receiving, by thefirst entity user access device, a tracking update on the ID node ifauthorized by the initial privilege.

At step 6515, method 6500 continues by receiving the authorization andthe initial privilege from the server, and then associating the firstentity user access device with the ID node at step 6520. At step 6525,method 6500 continues with the first entity user access device receivingdata collected by the ID node if authorized by the initial privilege.

At step 6530, method 6500 concludes by managing the data collected bythe ID node. For example, in one embodiment, the managing step mayfurther comprise managing where the data collected by the ID node ismaintained in accordance with the initial privilege. For instance, theinitial privilege may allow the data collected by the ID node to beuploaded by the first entity user access device to the server over thefirst communication path.

Additionally, method 6500 may also include where the initial privilegeno longer authorizes the first entity user access device to receive thedata collected by the ID node once the ID node associates with ashipping entity master node.

Those skilled in the art will appreciate that method 6500 as disclosedand explained above in various embodiments may be implemented on amaster node (such as exemplary master node 110 a as illustrated in FIG.4 when implemented with a sender's user access device, such as device200 in FIG. 17), running one or more parts of a control and managementcode (such as code 425) to implement any of the above describedfunctionality. Such code may be stored on a non-transitorycomputer-readable medium (such as memory storage 415 in an exemplarydevice 200 operating as a master node). Thus, when executing such code,a processing unit of the device (such as unit 400) may be operative toperform operations or steps from the exemplary methods disclosed above,including method 6500 and variations of that method.

FIG. 66 is a flow diagram illustrating an exemplary method formulti-entity management of an ID node in a wireless node network fromthe perspective of recipient entity in accordance with an embodiment ofthe invention. Referring now to FIG. 66, method 660 begins at step 6605by executing a program module of code (such as code 425) on a recipiententity user access device to enable operation of the recipient entityuser access device as a master node. As such, the recipient entity useraccess device is operative to communicate directly with a server over afirst communication path (as a master node) and separately communicatewith the ID node over a second communication path (as a master node).The ID node is operative to communicate directly with the recipiententity user access device over the second communication path but unableto directly communicate with the server.

At step 6610, method 6600 continues by transmitting a request to theserver from the recipient user access device. The request is for anauthorization to associate with the ID node and a destination privilegerelated to data to be collected by the ID node. In one embodiment, theauthorization and the destination privilege are separate data items,however in other items both are implemented as part of the authorization(e.g., the destination privilege may be a specific authorized task orprivilege approved by the server to be performed between the master nodeand the ID node).

In one embodiment, the destination privilege may comprise a paidprivilege. In more detailed embodiment, the destination privilege maycomprise a paid privilege to access only a limited portion of the dataconnected by the ID node. And in another embodiment, the destinationprivilege may allow the data collected by the ID node to be uploaded bythe recipient user access device to the server over the firstcommunication path.

At step 6615, method 660 continues by receiving the authorization andthe destination privilege from the server. At step 6620, method 660 thenassociates the recipient user access device with the ID node. And atstep 6625, method 6600 concludes with the recipient user access devicereceiving data collected by the ID node if authorized by the destinationprivilege.

In a further embodiment, method 660 may have management of the datacollected by the ID node to be limited to the server if the datacollected by the ID node is not authorized to be received by therecipient user access device under the destination privilege.

Those skilled in the art will appreciate that method 6600 as disclosedand explained above in various embodiments may be implemented on amaster node (such as exemplary master node 110 a as illustrated in FIG.4 when implemented with a recipient's user access device, such as device205 in FIG. 17), running one or more parts of a control and managementcode (such as code 425) to implement any of the above describedfunctionality. Such code may be stored on a non-transitorycomputer-readable medium (such as memory storage 415 in an exemplarydevice 200 operating as a master node). Thus, when executing such code,a processing unit of the device (such as unit 400) may be operative toperform operations or steps from the exemplary methods disclosed above,including method 6600 and variations of that method.

An ID node managed by multiple entities using a wireless node network isdescribed in another embodiment. The ID node comprises at least a nodeprocessing unit, a node memory coupled to the processing unit, and ashort-range communication interface coupled to the node processing unit.The node memory maintains code for execution by the processing unit anddata collected by the ID node during operations of the node. And theshort-range communication interface is operative to directly communicatewith a master node in the network over a short-range communication pathbut unable to directly communicate with a server in the network.

The node processing unit of the ID node, when executing the codemaintained on the node memory, is operative to associate the ID nodewith a first entity user access device, where the first entity useraccess device operates as the master node and can communicate directlywith the server over a longer range communication path and separatelycommunicate with the ID node over the short-range communication path.

The node processing unit is also operative to provide the first entityuser access device with access to the data collected by the ID node ifauthorized by an initial privilege, which was provided by the server tothe first entity user access device. In one embodiment, the initialprivilege may comprise a paid privilege to access the data collected bythe ID node. In another embodiment, the initial privilege may comprise apaid privilege to be provided a location of the ID node. In yet anotherembodiment, the initial privilege may comprise a paid privilege to trackan item associated with the ID node over time.

In still another embodiment, the initial privilege may be related tomanaging the data collected. For example, one embodiment of the initialprivilege may comprise a privilege for the first entity user accessdevice to manage where the data collected by the ID node is stored, suchas uploaded from the node memory to the first entity user access deviceover the short-range communication path via the short-rangecommunication interface. In another embodiment, the initial privilegemay comprise a privilege to have the data collected by the ID nodeuploaded to the server from the first entity user access device over thelonger range communication path.

The node processing unit is also operative to associate the ID node witha shipping entity master node in the network. In one embodiment, thenode processing unit may be further operative to restrict the firstentity user access device from directly accessing the node memory forthe data collected by the ID node after the ID node is associated withthe shipping entity master node.

The node processing unit is operative to provide the associated shippingentity master node with access to the data collected by the ID nodebased upon a transferred privilege, which was provided by the server tothe shipping entity master node. The node processing unit is thenoperative to associate the ID node with a second entity user accessdevice, where the second entity user access device operates as anothermaster node and can communicate directly with the server over the longerrange communication path and separately communicate with the ID nodeover the short-range communication path.

And finally, the node processing unit is also operative to provide theassociated second entity user access device with access to the datacollected by the ID node if authorized by a destination privilegeprovided by the server to the second entity user access device. In oneembodiment, the destination privilege may comprise a paid privilege toaccess any of the data collected by the ID node. In another embodiment,the destination privilege may comprise a paid privilege to access only alimited portion of the data connected by the ID node. And in stillanother embodiment, the data collected by the ID node while the ID nodeis associated with the shipping entity master remains owned by ashipping entity related to the shipping entity master node when thesecond entity user access device is not authorized by the destinationprivilege.

In a further embodiment, the node processing unit may also be furtheroperative to request a system update regardless of where the datacollected by the ID node is stored.

Dynamic Node Adaption within a Wireless Node Network

As noted in the logistics examples described above, an embodiment of anode may operate in different ways depending upon its desiredapplication. For example, a master node may have different operatingmodes—one that is typically a default or normal operating mode where itis able to locate itself and operate as a higher level node in thewireless node network. However, under certain circumstances, anexemplary master node may change to an alternative operating mode andessentially function similar to a lower level node in the wireless nodenetwork. This may happen on a temporary basis when an environmentalchange is detected, such as when the master node loses GPS signal lockand can no longer detect location signals with which to determine itsown location. Rather than simply go inoperative, an embodiment of amaster node advantageously alters its operating mode to a temporary IDnode mode, and continues operations within the wireless network as anon-locating type of master node (e.g., it may be able to stillcommunicate with the server but is unable to self-locate). Thus, anembodiment may allow a master node that becomes “lost” due toenvironmental circumstances to remain functional in the network,associate with other nodes, help transfer shared data throughconnections with other nodes, and revert back to its normal operationwhen the master node is able to locate itself again.

As previously noted, exemplary master nodes 110 a, 110 b, 110 cillustrated in FIG. 2 are deployed and connected to network 105 (and byvirtue of those respective connections, to server 100) as well as toeach other. ID nodes 120 a, 120 b, 120 e are connected to various masternodes. However, ID nodes 120 c and 120 d are shown in FIG. 2 connectedto ID node 120 b but not to any of the master nodes. This may be thecase if ID nodes 120 b, 120 c, 120 d are associated with different items(e.g., packages) within a larger container 210 (or grouped together on apallet). In such an embodiment, only ID node 120 b remains within thewireless communication range of any master node. However, in oneembodiment, ID node 120 b may actually be a different master node that,because it is placed within container 210 and shielded from receivinglocation signals, is operating in an alternative mode to functiontemporarily as an ID node (e.g., ID node 120 b shown in FIG. 2). Whilethe master node (operating as ID node 120 b) remains in container 210,it may be unable to operate as a master node and may operate as an IDnode (a master node operating in a temporary ID node mode) that canremain in a communication relationship with ID nodes 120 c and 120 d.After changing operational modes, node 120 b (the master node operatingin a temporary ID node mode) may associate with another master node(such as master node 110 b) and forward information from ID nodes 120 c,120 d. But after being removed from within container 210, node 120 b mayrevert back to the normal operating mode of a master node.

FIGS. 20 and 21 are flow diagrams illustrating various exemplary methodsfor dynamically changing an operational mode of node operations in awireless node network. Those skilled in the art will appreciate thateach of these exemplary methods for dynamically changing a configurationof one or more nodes in a wireless node network may be implemented byinstructions stored on a non-transitory computer-readable medium, whichwhen executed perform the steps of the respective method.

Referring now to FIG. 20, exemplary method 2000 begins at step 2005where a first of the master nodes detects an environmental changerelated to a first of the master nodes (e.g., no longer being able toreceive a location signal). In a more detailed example, theenvironmental change may be when at least the first of the master nodesis within a container that substantially impedes reception of thelocation signal by the first of the master nodes. In other words, thefirst master node may no longer be able to determine its own locationbecause of a change in the surrounding environment, such as materialsnear or around the master node or building structure that acts as ashield to prevent or operatively impair reception of location signals(e.g., GPS signals).

In a further example, the environmental change may be an anticipatedenvironmental change related to the first of the master nodes. Forexample, the server may notify the first of the master nodes that it isabout to be placed within a container. Thus, the first of the masternodes becomes aware of the upcoming environmental change and may includesteps to complete urgent tasks (e.g., sharing of data, completinglocating tasks, etc.) prior to the experiencing the differentenvironmental.

In response to detecting the environmental change, the method 2000 hasthe first of the master nodes changing its operational mode to atemporary ID node mode where the first of the master nodes no longer canself-determine its location at step 2010. In one embodiment, thetemporary ID node mode may have the first of the master node performingall normal operations of an exemplary higher level node in the network(compared with the ID node) that do not rely upon self-determinedlocations. For example, the master node operating in the temporary IDnode mode may be able to communicate with the server while not beingable to self-locate like a normal master node. In another embodiment,the temporary ID node mode may have the first of the master nodesoperating in a more limited way so as to mimic an ID node (e.g., with analtered signature to broadcast when advertising) so that other masternodes will believe the master node operating in the temporary ID nodemode is an ID node for purposes of associating (passive or active).

And in a further embodiment, the first of the master nodes may operatingin the temporary ID node mode while remaining in a communicationrelationship with at least one ID node. Thus, for example, when a masternode is placed in an adverse RF environment and loses reception of itslocation signals, the master node may remain associated (e.g., an activeauthorized connection) with this ID node.

At step 2015, method 2000 continues by notifying the server by the firstof the master nodes that the first of the master nodes is operating inthe temporary ID node mode. And at step 2020, method 200 concludes byassociating the first of the master nodes operating in the temporary IDnode mode with a second of the master nodes. Such associating may beaccomplished by the first of the master nodes advertise to the second ofthe master nodes regarding a request to connect with the second of themaster nodes, receiving a response from the second of the master nodes,and sending a reply to the second of the master nodes with informationrequested.

Method 2000 may further include forwarding information (e.g., sensordata) gathered by the ID node to the second of the master nodes via thefirst master node operating in the temporary ID node mode. In moredetail, the master node operating in the temporary ID node mode mayprovide extended visibility to other ID nodes (e.g., ID nodes 120 c and120 d within container 210) and relay or forward information from thoseID nodes not in direct contact with the second master node (and thus theserver).

Additionally, method 2000 may also include changing the operational modefor the first of the master nodes to a normal operational mode upondetecting a second environmental change related to the first of themaster nodes, the normal operational mode being where the first of themaster nodes can self-determine its location again. Thus, the first ofthe master nodes may adapt and still be useful in the wireless nodenetwork when an environmental change limits certain functionality of themaster node (e.g., its self-locating ability) until the environmentrelated to the master node changes again and that functionality is nolonger limited.

Those skilled in the art will appreciate that method 2000 as disclosedand explained above in various embodiments may be implemented on anexemplary master node, such as master node 110 a illustrated in FIG. 4,running one or more parts of master control and management code 425 toimplement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium such as memorystorage 415 on a master node (such as master node 110 a). Thus, whenexecuting code 425, the master node's processing unit 400 may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 2000 and variations of that method.

While FIG. 20 illustrates exemplary steps from method 2000 from theperspective of master node actions and steps, FIG. 21 illustrates andprovides an explanation of an exemplary embodiment where a method formanaging a dynamically changing operational mode of node operations in awireless node network may occur from the perspective of server actions.Referring now to FIG. 21, exemplary method 2100 begins at step 2105 byreceiving a notification by the server from a first of the master nodesreporting an environmental change related to the first of the masternodes. In one example, the environmental change may be an anticipatedenvironmental change related to the first of the master nodes. In moredetail, the anticipated environmental change may comprise, for example,an adverse RF environment anticipated to be exposed to the first of themaster nodes (such when the first of the master nodes is anticipated tobe moved within a container, such as a ULD, that may impede reception ofa location signal (such as a GPS signal) by the first of the masternodes).

In another embodiment, method 2100 may also have the server updatingcontext data consistent with the environmental change. For example, whenthe first master node is placed in the ULD and it loses reception of GPSsignals, the server updates relevant types of context data to reflectthis environmental change related to the first master node.

At step 2110, method 2100 continues by recording a logical change of thefirst of the master nodes to be operating in a temporary ID node mode asa result of the environmental change. For example, the logical changeessentially has the first master node temporarily operating in thetemporary ID node mode with ID node like features as a result of, forexample, a detected lack of location signal reception (e.g., GPS signalloss), being exposed to an adverse RF environment that impedes receptionof a location signal, being in a container that shields an interior ofthe container from reception of the location signal, being in a shieldedstructure (e.g., indoors within a building where GPS signals aredifficult to pick up), and being substantially near shielding material(e.g., being placed next to metal objects that may adversely interferewith RF signal reception). In another embodiment, the temporary ID nodemode may be characterized as still allowing the first of the masternodes to communicate with the server while no longer being able toself-determine its location.

At step 2115, method 2100 concludes by authorizing the first of themaster nodes operating in the temporary ID node mode to associate with asecond of the master nodes. In an airborne example, the second masternode may be a dedicated master node within an aircraft that has locationcircuitry and an antenna on the outside of the aircraft so that itmaintains GPS signal lock yet allows the second master node tocommunicate with nodes inside onboard containers (e.g., the first masternode that is operating in the temporary ID node mode as a result of itsinability to detect GPS signals within the container). In one example,method 2100 may also include receiving information (e.g., sensor datagathered by a node or other shared data) from the second of the masternodes as forwarded information from the first of the master nodes whenoperating in the temporary ID node mode

In another embodiment, method 2100 may also include recording anotherlogical change of the first of the master nodes back to a normaloperational mode as a result of a second environmental change related tothe first of the master nodes. For example, the first of the masternodes may now be removed from being within a ULD container. As a result,the first of the master nodes may adaptively change back to its normaloperational mode where it can self-determine its location again.

Those skilled in the art will appreciate that method 2100 as disclosedand explained above in various embodiments may be implemented on anexemplary server, such as server 100 illustrated in FIG. 5, running oneor more parts of server control and management code 525 to implement anyof the above described functionality. Such code may be stored on anon-transitory computer-readable medium such as memory storage 515 on aserver (such as server 100). Thus, when executing code 525, the server'sprocessing unit 500 may be operative to perform operations or steps fromthe exemplary methods disclosed above, including method 2100 andvariations of that method.

Similar to such exemplary methods, an exemplary dynamically configurablewireless node network is disclosed. The exemplary network comprises aplurality of master nodes and a server in communication with the masternodes. The master nodes include at least a first master node and asecond master node. Each of the master nodes is a higher complexity node(compared with an ID node) and has a normal operating mode where therespective master node is operative to determine its own position(amongst other functions). The master nodes also have a temporary IDnode mode where the respective master node is no longer operative todetermine its own position.

The first master node is operative to detect an environmental changerelated to the first master node and temporarily alter a currentoperating mode of the first master node from the normal operating modeto the temporary ID node mode. The second master node, when operating inthe normal operating mode, is operative to associate with the firstmaster node when the first master node is operating in the temporary IDnode mode. In a further embodiment, the first master node operating inthe temporary ID node mode may be further operative to return tofunctioning as the first master node in the normal operating mode upondetecting a second environmental change. The second environmental changemay be when the first master node receives a location signal to allowthe first master node to determine its own location and return tofunctioning as the first master node in the normal operating mode. Inyet another embodiment, the first master node may also be operative,when operating in the temporary ID node mode, to receive sensorinformation and forward the sensor information to the second masternode. This sensor information may be sensor data received from an IDnode that remained in communication with the first master node, evenafter the first master node changed to operating in the temporary IDnode mode.

In one embodiment, the server may be operative to receive a notificationfrom the first master node reporting the environmental change, record alogical change of the first master node to be operating in the temporaryID node mode, and authorize the second master node to associate with thefirst master node when the first master node is operating in thetemporary ID node mode. For example, the server may upon receipt of thenotification and recording the logical change, instruct other masternodes to recognize a signature or identification of the first masternode as a type of ID node for purposes of node management, association,location determination, and sharing of information.

In another embodiment, the environmental change comprises an inabilityof the first master node to sufficiently receive and determine aposition based upon a location signal (such as a GPS signal). In moredetail, the environmental change may further comprise the first masternode being exposed to an adverse RF environment (such as being placednear shielding material) that impedes reception of the location signalby the first master node.

While the above examples relative to FIGS. 20 and 21 describeembodiments where a master node may operate in a temporary ID node modedepending upon its desired application, FIGS. 95-97 describe additionalembodiments where an ID node may be adapted to operate in a differentmode, such as a pseudo master node mode that avoids the need for an IDnode to communicate through an intermediary node when messaging theserver. For example, an ID node may typically operate in a default ornormal operating mode where it is unable to self-determine its locationas well as limit direct communication to a short range communicationpath (e.g., Bluetooth®). However, in some situations, the ID node may beadapted and operative to communicate on other communication paths, suchas a longer range communication path directly to the server without theneed for an intermediary node (e.g., a master node) when desiring toforward information from the ID node to the server. Additionally, whilethe ID node in such a pseudo master node mode may still be limited inits inability to self-determine location (e.g., the ID node would remainwithout location circuitry, such as GPS circuitry), such an ID node mayprovide master node like connectivity for other ID nodes in the networkin order to enhance the ability to report on relevant node informationfrom one or more ID nodes to the server. Further, while the pseudomaster node may not have the ability to self-determine location absentinput from other nodes in one exemplary embodiment, such a pseudo masternode may still be aware of what nodes are in its proximity.

FIG. 95 is a diagram illustrating an exemplary ID node device similar toID node 120 a shown in FIG. 3, but further adapted to operate in apseudo master node mode in accordance with an embodiment of theinvention. Referring now to FIG. 95, exemplary ID node 95-120 a is shownthe same as illustrated in FIG. 3 but with an additional communicationinterface 9500 (e.g., an LTE radio using Internet Protocol version 6 orIPv6), which enables the ID node 95-120 a to send and receive messagesover a medium/long range communication path (e.g., a WiFi path to theInternet) rather than have to rely solely upon a shorter rangecommunication path (e.g., a Bluetooth® formatted short range path). Inthis embodiment, the specially adapted ID node 95-120 a may thus beoperative to report relevant node information (such as sensor data) to aserver in a wireless node network in a much more efficient manner. Inother words, when deployed as part of an exemplary hierarchical wirelessnode network of ID nodes, master nodes, and a server, the speciallyadapted ID node 95-120 a may enable a more robust yet more economicalsolution for node communication without the need for relying onintermediary nodes (such as a master node) for such communicationpurposes.

FIG. 96 is a diagram illustrating such an exemplary hierarchicalwireless node network in accordance with an embodiment of the invention.Referring now to FIG. 96, an exemplary system of network devicesdeployed within an exemplary hierarchical wireless node network 9600 isillustrated having three different levels of network devices. Generally,a first level includes ID nodes (more basic and less costly network nodedevices), a next level up includes master nodes (more sophisticated withthe ability to self-locate using dedicated positioning or locationcircuitry onboard the node), and then a top level that includes a moresophisticated server. Normally, devices in each level can communicatewith those devices in the next level above or below in the systemhierarchy. However, when an ID node is adapted to operate in a pseudomaster node mode by having the ability to also communicate with aserver, it effectively bypasses the need to have a master node in anintermediary role and, at times, can provide more efficientcommunication back to the server. Thus, the ability for an ID nodeoperate in a pseudo master node mode as described herein improves theoverall operation of a wireless node network and applications that usesuch wireless node networks (e.g., technical fields such as logistics,shipping management, inventory management, and the like). In otherwords, the exemplary embodiments described herein with one or more IDnodes that can operate in a pseudo master node mode along with a masternode and server, provide a type of specially-adapted system within ahierarchical wireless node network that enhances and improvescommunications in the network, which results in more efficientoperations in technical fields such as logistics, shipping management,retail inventory management, and the like.

In more detail, on a first level of the exemplary hierarchical wirelessnode network 9600, FIG. 96 shows multiple ID nodes, such as ID node 120b, ID node 120 c, and ID node 95-120 a. While ID node 120 c is not shownassociated with a particular package, ID node 120 c and ID node 95-120 aare respectively shown disposed within packages 9620 and 9625.Additionally in this embodiment, while ID node 120 c is shown not havingsensors, ID nodes 120 b and 95-120 a each include a respective set ofsensors 360 similar to those described with respect to FIG. 3. Thesensors 360 (e.g., temperature, light, or moisture sensors) typicallygenerate sensor data (e.g., sensor data 350) in operation. As such, thesensor data may be related to at least one condition of the respectivepackages. Such sensor data is a type of relevant node information thatmay be useful to quickly have available at the backend server (e.g.,server 100).

In the same example shown in FIG. 96, a second level of the network 9600is populated with at least one master node (such as master nodes 110 aand 110 b). As shown in FIG. 4, such a master node may include specificlocation circuitry (such as GPS circuitry 475) with which toself-determine its location. In other words, a master node can determineits own position without reliance on input from other network nodes. Andadditionally, as discussed in more detail above, these master nodes areadapted and operative to associate with ID nodes that are within acommunication range of the respective master nodes.

And in the example shown in FIG. 96, a third level of the network 9600is populated with a server, such as server 100. FIG. 5 and the textualdescription accompanying FIG. 5 above provides more detail on such aserver. As shown in FIG. 96, server 100 may communicated with othernodes in the network 9600 over network 105.

In operation, an embodiment of network 9600 allows for robustcommunication between the network devices shown in FIG. 96 and describedabove. In one embodiment, ID node 95-120 a is adapted and operative toperform certain functions related to node communication as it isdisposed within such a network 9600. In more detail, ID node 95-120 a isadapted and operative to associate itself with master node 110 a. Doingso allows for ID node 95-120 a to determine its location with help frommaster node 110 a using one of the node locationing techniques describedherein. Thus, ID node 95-120 a is unable to self-determine its location.

ID node 95-120 a may also be adapted and operative to capture relevantnode information. In a general embodiment, relevant node information maybe information generated or gathered by a node in the network 9600 wherethe information is related to operations of the network or itemsassociated with the network (such as packages in transit that areassociated with and monitored with sensors in certain nodes). In moredetail, the relevant node information in an embodiment may comprise atleast one of profile data, security data, association data, shared data,and sensor data. Examples of such profile data, security data,association data, shared data, and sensor data are respectivelydescribed above relative to FIGS. 3 and 95, which include profile data330, security data 335, association data 340, shared data 345, andsensor data 350 as examples of relevant node information.

Such relevant node information may be captured directly by ID node95-120 a or more indirectly by another node that provides suchinformation to ID node 95-120 a. For example, ID node 95-120 a maycapture relevant node information using sensors 360 onboard ID node95-120 a. Such sensors 360 in node 95-120 a may detect informationrelated to package a condition of package 9625.

In another example, ID node 95-120 a may associate with another ID node120 b (e.g., via passive association or active association) and receiveother relevant node information from the other ID node 120 b over ashort range communication path 9610 (e.g., Bluetooth® radio path). Inthis way, ID node 95-120 a may capture the other relevant nodeinformation from a broadcast signal originating from ID node 120 b. Suchother relevant node information may include information about thecondition of package 9620.

ID node 95-120 a may also be adapted and operative to transmit, in apseudo master node mode, the relevant node information to the server 100without using a master node (e.g., master nodes 110 a, 110 b) as anintermediary to the server 100. Those skilled in the art will appreciatethat arming the master nodes in a wireless node network may haveadvantages when consolidating and managing communications with theserver in the network, but that deploying an ID node at a lower levelthat can communicate with the server directly (i.e., without using amaster node as an intermediary network device or node in communicationswith the server) may also allow for situations where a master node maybe temporarily offline, out of communication range to the ID node, orwhen the relevant node information may be more efficiently sent to theserver directly. Accordingly, an exemplary pseudo master node mode foran ID node is a mode of operation that enables such directcommunications to the server (as a master node normally does) butadvantageously does not require the ID node to self-determine itslocation or position (which would otherwise require dedicated locationcircuitry onboard the ID node). Thus, such an ID node as ID node 95-120a operates like a typical master node with respect to its ability tocommunicate with the server but still operates like a typical ID nodewith respect to self-locating.

In a more detailed embodiment, ID node 95-120 a may be adapted andoperative to transmit such relevant node information by generating amessage for the server and then broadcasting the message on a longerrange communication path. In this embodiment, the message includes therelevant node information and is formatted for the longer rangecommunication path (such as a longer range WiFi path) when compared to ashorter range communication path (such as a short range Bluetooth® path)used to communicate between the ID nodes. Broadcasting the message onthe longer range communication path to the server 100 can be done whileavoiding the need to first send the message to a master node (such asmaster node 110 a or 110 b) during transit to the server 100.

In still another detailed embodiment, ID node 95-120 a may be adaptedand operative to transmit such relevant node information by firstdetermining a desired communication path for a message including therelevant node information. The desired communication path may be eithera first communication path or a second communication path. The firstcommunication path includes one of the master nodes (such as master node110 a or master node 110 b) operating as an intermediary to the server100, while the second communication path does not include and avoids theneed for a master node operating as an intermediary to the server 100.

In this other detailed embodiment, ID node 95-120 a may be furtheradapted and operative to transmit such relevant node information by thenformatting the message for the server and broadcasting it. In thisembodiment, the format of the message is one suitable for broadcastingon the determined desired communication path. Thus, when broadcastingthe message on the second communication path to the server, suchbroadcasting may avoid the need to first send the message to the masternode during transit to the server.

FIG. 97 is a flow diagram illustrating an exemplary method for enhancednode communication within a hierarchical wireless node network having aplurality of ID nodes on a first level, a master node on a second level,and a server at a third level in accordance with an embodiment of theinvention. Referring now to FIG. 97, method 9700 begins at step 9705 byassociating a first of the ID nodes with the master node. The first IDnode is unable to self-determine its location while the master node isadapted to self-determine its location via location circuitry.

Method 9700 continues at step 9710 with the first ID node capturingrelevant node information. As described above with respect to FIG. 96,an embodiment may have the relevant node information comprising at leastone of profile data, security data, association data, shared data, andsensor data. In more detail, the sensor data may comprise data collectedfrom one or more sensors in communication with the first of the IDnodes. For example, the sensor data may include temperature and moisturedata collected from sensors 360 operatively coupled through interfacingand buffering circuitry onboard ID node 95-120 a as shown in FIG. 96. Assuch, the data collected from the one or more sensors may relate to oneor more conditions of a package 9625 associated with the first ID node(i.e., ID node 95-120 a).

In a further embodiment of method 9700, the capturing step may furthercomprise the first ID node capturing the relevant node information froma broadcast originating from a second of the ID nodes associated withthe first of the ID nodes. As such, the sensor data may include datacollected from one or more sensors in communication with the second ofthe ID nodes. For example, the sensor data may include temperature datacollected from sensors 360 operatively coupled through interfacing andbuffering circuitry onboard ID node 120 b (as a second ID node) as shownin FIG. 96. As such, the data collected from the one or more sensors mayrelate to one or more conditions of a package 9620 associated with thesecond ID node (i.e., ID node 120 b).

Method 9700 concludes at step 9715 with the first ID node operating in apseudo master node mode in the hierarchical wireless node network totransmit the relevant node information to the server without using themaster node as an intermediary to the server. As previously noted, thismay be advantageous to exclude the master node as an intermediary insome circumstances where speed is more important or access to a masternode may be somewhat impaired.

In a further embodiment of method 9700, the transmitting step may beimplemented with the first ID node generating a message for the serverand broadcasting the message to the server. The message may include therelevant node information and be formatted for a longer rangecommunication path when compared to a shorter range communication pathused to communicate between the ID nodes. The message may be broadcastby the first ID node on the longer range communication path to theserver while advantageously avoiding the need to first send the messageto the master node during transit to the server.

In yet another more detailed embodiment of method 9700, the transmittingstep may have the first ID node determining a desired communication pathfor a message including the relevant node information. The desiredcommunication path may include one of a first communication path and asecond communication path, where the first communication path includesthe master node operating as a communication intermediary to the server.In contrast, the second communication path would not include the masternode operating as the intermediary to the server. Next, the ID nodeformats the message for the server according to the desiredcommunication path and then broadcasts the message on the desiredcommunication path to the server while avoiding the need to first sendthe message to the master node during transit to the server when thedesired communication path is the second communication path.

Those skilled in the art will appreciate that method 9700 as disclosedand explained above in various embodiments may be implemented on an IDnode (such as exemplary ID node 95-120 a as illustrated in FIGS. 95-96)running one or more parts of a control and management code (such as code325) to implement any of the above described functionality. Such codemay be stored on a non-transitory computer-readable medium (such asmemory storage 315 in an exemplary ID node). Thus, when executing suchcode, a processing unit of the node (such as unit 300) may be operativeto perform the method and various steps as disclosed above.

In still another series of embodiments, a node may have the ability toadaptively change or alter its advertising message format as a way ofenhancing system operations within a wireless node network. Embodimentsmay change the message format to one of various different types ofshortened formats (i.e., also called a variable broadcast format)depending upon, for example, a desired degree of change from afull-format that provides a larger amount of information balancedagainst a shortened format that may specifically identify thebroadcasting node to certain other nodes with less informationbroadcasted.

In particular, FIGS. 98A-98C, FIG. 99, and FIG. 100 describe additionalembodiments where an exemplary node (e.g., an ID node or master node)may change its advertising message broadcast format when the nodechanges state, such as when a change in the relative environment of thenode is detected. In general, once such a changed state is detected(e.g., a change in node density near the node or a change in how thenode may be moving), the node may be adapted to communicate in adifferent or alternative format, such as a shortened or truncated formatwhen compared to an initial or first format for the advertising message.By dynamically altering how the node formats an advertising messagedepending upon changes in the relative environment of the node, the nodeallows for more compact and efficient communication in the wireless nodenetwork within which the node operates and enhanced system operation.More particularly, embodiments of such a dynamic altering of nodeadvertising message format may allow for shorter communication bursts,which accommodates system operations when there is a relatively highdensity of nodes operating in a given area.

Those skilled in the art will appreciate that an embodiment may have thenode detecting a state change and then, in response, altering itsadvertising message broadcast format by itself, while other embodimentsmay have the broadcasting node (e.g., an ID node) receiving a control orcommand message from another node (e.g., a master node) that causes thebroadcasting node to change or alter its advertising message broadcastformat to a type of shortened format (e.g., a global shortened format, anested shortened format, or a local shortened format).

FIGS. 98A-98C present a series of exemplary diagrams that generallyillustrate various embodiments where an exemplary node adaptively altershow it formats a broadcasted advertising message in response to detectedstate changes for the node. Referring now to FIG. 98A, an exemplary node(i.e., ID node 120 a) is shown in motion as it approaches a conveyorsystem 9805, which has a moving conveyor belt 9800. The exemplary node120 a may be associated with a package, container, vehicle, or otherobject or person in motion. And as explained with reference to FIG. 3,the exemplary node 120 a may have at least a processing unit 300,volatile memory 320, memory storage 315, and a communication interface375 for communicating with other nodes (such as master node 110 a, whichis further operative to communicate with server 100). In an embodiment,an exemplary adaptive messaging program section may be implemented aspart of node control and management code 325, which is maintained in thenode's memory storage 315. The exemplary adaptive messaging program codesection implements and controls how node 120 a may generate anddynamically format advertising messages being broadcast from node 120 avia Bluetooth® Low Energy (BLE) wireless signals 9810 being transmittedfrom the communication interface on node 120 a. The exemplary adaptivemessaging program code section may, in some embodiments, implements andcontrols how node 120 a may respond to commands, messages or othersignals received from other nodes that responsively cause node 120 a togenerate and dynamically format advertising messages being broadcastfrom node 120 a

In an embodiment and in light of the ID node functionality discussionabove related to FIG. 3, node 120 a shown in FIG. 98A may be adapted andoperative to load the adaptive messaging program section into the node'svolatile memory and, when executing at least the adaptive messagingprogram code section when resident in the node's volatile memory, node120 a is further adapted and operative to dynamically format advertisingmessages. In more detail, an embodiment of the processing unit in node120 a running the adaptive messaging program code section is adapted andoperative to generate an advertising message in a first format (e.g.,such as the full format shown and illustrated with respect to FIGS. 6-7)and cause the communication interface to broadcast the advertisingmessage in the first format when the node device is in a first state.For example, as shown in FIG. 98A, node 120 a is in a state of transitas it moves towards conveyor system 9805. As the node 120 a approachedthe conveyor system 9805, the node 120 a may begin broadcasting anadvertising message in a normal format as it attempts to associate withmaster node 110 a. Thus, the state or, more specifically, the relativeenvironment of the node 120 a is that node 120 a is moving in transitand approaching conveyor system 9805.

FIG. 98B illustrates the same embodiment as shown in FIG. 98A, but afterthe node 120 a has detected a state change associated with a changedrelative environment of the node 120 a. This may be accomplished whenthe node 120 a switches between broadcasting the advertising message ina first (e.g., full length) format and scanning or listening for ananticipated or known node signature indicative of a type of changedrelative environment of the node 120 a. Upon detection of such a nodesignature while scanning, node 120 a detects such a state change. Asshown in FIG. 98A, an embodiment may have node 120 a detecting the nodesignature of master node 110 a as a state change as node 120 aapproaches conveyer system 9805 given that master node 110 a isassociated with the system 9805. Thus, simply detecting the signature ofmaster node 110 a may be enough to indicate a change in the relativeenvironment surrounding node 120 a in one embodiment.

Referring back to the example shown in FIG. 98B, another embodiment hasnode 120 a detecting a different movement aspect in that it has beenplaced on a moving conveyor belt 9800 of conveyor system 9805 and is nolonger moving in transit approaching the conveyor system 9805. Thus, inthis example embodiment, the changed relative environment of node 120 amay be from a detected change in the movement aspect of node 120 a—suchas whether the node 120 a is moving relative to known structure. Suchdetection may be accomplished, for example, by receipt of a signal withlocation and/or context information from another node (e.g., master node110 a) or by reference to location and/or context information maintainedby the node itself. In still another embodiment, the changed relativeenvironment may be from a detected change in a node density near thenode 120 a—such as whether node 120 a is entering an area having a verylarge number of other nodes (e.g., a container or ULD).

In more detail, the change in the movement aspect of node 120 a shown inFIG. 98B may be considered to reflect that the node 120 a issubstantially stationary relative to some proximate structure, such asthe conveyor belt 9800. In an embodiment such as that illustrated inFIG. 98B, the proximate structure to the node (e.g., conveyor belt 9800)may be moving while being substantially stationary relative to the nodedevice (e.g., node 120 a placed on the belt 9800). In anotherembodiment, such proximate structure may be stationary along with thenode (e.g., node 120 a placed in a temporary storage room). Thus, givensuch proximate structure may have known location information andattributes (e.g., linear speed of the belt, time it takes to transitfrom one point to another along the conveyor belt, the location orcontext information describing a temporary storage room, etc.), asimplified, shortened, truncated, or abbreviated format for furtheradvertising messages may be used given what is known or can be impliedabout the relative environment of the node.

In a more detailed embodiment, such proximate structure may comprise atleast one of a conveyance device associated with the node device or apackage containing device for the node device. For example, a conveyancedevice associated with the node that may help move the node may include,but is not limited to, a conveyor belt, a trailer, a truck, an aircraft,a train, and a delivery vehicle (e.g., a car, van, and the like). Inanother example, a package containing device may include, but is notlimited to, a facility, room, bin, container, pallet, or a unit loaddevice (ULD) type of transportation storage. Such package containingdevices are generally able to take on and have temporary custody of thenode device while such conveyance devices are generally able to move thenode device between locations.

To adapt to the detected state change of node 120 a, an embodiment ofthe processing unit in node 120 a running the adaptive messaging programcode section is adapted and operative to alter the first format of theadvertising message to a shortened format comprising an identifier fornode device, where the identifier is derived from the changed relativeenvironment of the node device; and then causing the communicationinterface to broadcast the advertising message using the shortenedformat.

In an embodiment, the shortened format is relative to the standard orlonger format used for advertising messages. Essentially, the shortenedformat allows for the recipient of an advertising message using theshortened format to be informed of which node is advertising and thechanged state for that node. Thus, an abbreviated message may begenerated according to the shortened format, which is then used when thenode processing unit causes further advertising messages to be broadcastby the communication in that shortened format.

FIG. 98C illustrates the same embodiment as shown in FIGS. 98A and 98B,but after the node 120 a has detected a further state change associatedwith yet another changed relative environment of the node 120 a. In thisparticular example, node 120 a has detected a different movement aspectin that it is no longer on the moving conveyor belt 9800 of conveyorsystem 9805 and is now moving in transit away from the conveyor system9805. Thus, the node processing unit of node 120 a is further adaptedand operative to dynamically alter a variable broadcast format of theadvertising message when detecting at least one further state change ofthe node device. In one embodiment, the variable broadcast format of theadvertising message comprises two different formats—a longer format withmore information related to the node and a shorter format with less orminimal additional information related to the node. However, furtherembodiments may implement the variable broadcast format of anadvertising message with more than two different formats to best suitthe information needs balanced with the communication and node densityrequirements for the system.

FIG. 99 is a flow diagram illustrating an exemplary method for adaptivenode communication within a wireless node network having a plurality ofnodes in accordance with an embodiment of the invention. Referring nowto FIG. 99, exemplary method 9900 begins at step 9905 with a first ofthe nodes generating an advertising message in a first format. In oneexample, the first format for the advertising message is the format asshown in FIG. 6 or 7. Such a format provides valued information in theheader that can be useful as described herein relating to passiveassociation and communication aspects.

At step 9910, method 9900 continues with the first of the nodesbroadcasting the advertising message in the first format when the firstof the nodes is in a first state. As discussed above and shown in theembodiment illustrated in FIG. 98A, exemplary node 120 a broadcasts anadvertising message while in a state of transit as it moves towardsconveyor system 9805. The advertising message is in a normal format asit attempts to associate with master node 110 a. Thus, the first stateor, more specifically, the first relative environment of the node 120 aas shown in FIG. 98A is currently that node 120 a is moving in transitand approaching conveyor system 9805.

At step 9915, exemplary method 9900 continues by detecting a statechange for the first of the nodes. The state change is associated with achanged relative environment of the first of the nodes, such as a changein a node density near the first of the nodes or a change in a movementaspect of the first of the nodes. For a state change involving a changein the movement aspect of the node, a further embodiment may have thefirst of the nodes being substantially stationary relative to aproximate structure. In another embodiment, the proximate structure(e.g., a conveyor belt 9800) may be moving while being substantiallystationary relative to the first of the nodes (e.g., node 120 a placedon and supported by the moving conveyor belt 9800). In further examples,the proximate structure may comprise at least one of a packagecontaining device for the first of the nodes or a conveyance deviceassociated with the first of the nodes. In different embodiments, aconveyance device may include a conveyor belt, a truck, a trailer, anaircraft, a train, and a delivery vehicle. Further, in otherembodiments, the package containing device may include a facility, aroom, a bin, a container, a pallet, and a unit load device (ULD) type oftransportation storage.

If no state change is detected in step 9915, method 9900 proceeds backto step 9910 to continue broadcasting advertising messages in the firstformat. However, if a state change is detected, method 9900 proceeds tostep 9920 where method 9900 continues by adapting to the detected statechange by altering the first format of the advertising message to ashortened format. The shortened format may comprise an identifier forthe first of the nodes, where the identifier is derived from the changedrelative environment of the first of the nodes.

In a more detailed embodiment of method 9900, step 9920 may have thefirst of the nodes generating an abbreviated version of the advertisingmessage according to the shortened format, and then broadcasting theabbreviated version of the advertising message in response to detectingthe state change. In other words, one embodiment may simply shorten themessage using the shortened format (e.g., by simply cutting out certaininformation), but another embodiment may create a different abbreviatedversion of the full length message using the shortened format (e.g., byreplacing some of the information with more compact versions ofinformation in the shortened format rather than simply cutting it out).

At step 9925, method 9900 continues by detecting a further state change.If no further state change is detected in step 9925, method 9900proceeds back to step 9910 to continue broadcasting advertising messagesin the shortened format. However, if a further state change is detected,method 9900 proceeds to step 9930 where method 9900 continues bydynamically altering the format (also referred to as a variablebroadcast format in some embodiments) of the advertising message basedupon the detected further state change of the first of the nodes. Forexample, the format of the advertising message may be altered back tothe first format. However, in other embodiments the format of theadvertising message may be further varied to accommodate andcorresponding to a further change in the relative environment of thefirst of the nodes.

Those skilled in the art will appreciate that method 9900 as disclosedand explained above in various embodiments may be implemented on a node(such as exemplary ID node 120 a as illustrated in FIGS. 98A-98C)running one or more parts of a node control and management code (such asan exemplary adaptive messaging program code section implemented as partof node control and management code 325) to implement any of the abovedescribed functionality. Such code may be stored on a non-transitorycomputer-readable medium (such as memory storage 315 in exemplary IDnode 120 a). Thus, when executing such code, a processing unit of thenode (such as unit 300) may be operative to perform the method andvarious steps as disclosed in the various embodiments described above.

While FIG. 99 and method 9900 describe embodiments of operational stepstaken by an exemplary node that is, itself, broadcasting an advertisingmessage and changing the format of that message to a shortened format,other embodiments may have the broadcasting node responding toinstructions or command messages sent from another node as part ofadapting its variable broadcast format to a type of shortened format.For example, master node 110 a shown in FIG. 98A may detect thebroadcasted advertising message 9810 from ID node 120 a, detect a statechange of ID node 120 a when that node is placed upon conveyor system9805, and then may instruct ID node 120 a to broadcast using a shortenedformat. In such an example, master node 110 a may be adapted andoperative to control when and how the ID node 120 a broadcasts itsadvertising message, and may control which type of shortened format maybe useful to deploy under the particular circumstances faced by ID node120 a.

Notably, in an embodiment from the perspective where one node devicecontrols how another node adapts its advertising message format, masternode 110 a may be deployed as an example of such a controlling nodedevice. As explained with reference to FIG. 4, such an exemplary masternode 110 a may include a processing unit 400; a volatile memory 420coupled to the processing unit 400; a memory storage 415 coupled to theprocessing unit 400; and a communication interface (e.g., short rangecommunication interface 480) also coupled to the processing unit 400 andproviding access to other nodes (such as ID node 120 a) in a wirelessnode network. In this embodiment, an exemplary adaptive messagingprogram code section may be implemented as part of master control andmanagement code 425, which is maintained in the master node's memorystorage 415 and can be loaded into and executed by processing unit 400while in the volatile memory 420. The exemplary adaptive messagingprogram code section implements and controls how master node 110 a maydynamically control how another node (e.g., ID node 120 a) alters theformat of advertising messages being broadcast from that other node via,for example, Bluetooth® Low Energy (BLE) wireless signals 9810transmitted from node 120 a.

In an embodiment and in light of the master node functionalitydiscussion above related to FIG. 4, master node 110 a shown in FIG. 98Amay be adapted and operative to load the adaptive messaging program codesection into the master node's volatile memory 420 and, when executingat least the adaptive messaging program code section when resident inthe master node's volatile memory, master node 110 a may be furtheradapted and operative to dynamically control how another node formatsadvertising messages. In more detail, an embodiment of the processingunit in master node 110 a running the adaptive messaging program codesection may be adapted and operative to receive an indication from thecommunication interface, where the indication reflects that thecommunication interface detected an advertising message in a firstformat being broadcast by the ID node. For example, master node 110 amay detect advertising message 9810 being broadcast by ID node 120 a ina full format (e.g., similar to that shown in FIGS. 6-7).

The embodiment of the processing unit in master node 110 a running theadaptive messaging program code section may be adapted and operative todetect a state change relative to one of the nodes, such as ID node 120a. The state change detected may be associated with a changed relativeenvironment of the ID node 120 a. Based upon the detected state change,the processing unit is also adapted and operative to instruct thecommunication interface to broadcast a command to the one node thatcauses the one node to alter the first format of the advertising messageto a shortened format. The shortened format comprises at least anidentifier for the one node derived from the node's changed relativeenvironment.

In various embodiments, the changed relative environment may takedifferent forms. For example, in one embodiment, the changed relativeenvironment may be a change in a node density near the one nodebroadcasting the advertising message. In another embodiment, the changedrelative environment may be a change in a movement aspect of the node.Such a change in the movement aspect may reflect that the node issubstantially stationary relative to a proximate structure, which may bemoving while being substantially stationary relative to the broadcastingnode. The proximate structure may be a package containing device for thebroadcasting node (such as a facility, a room, a bin, a container, apallet, and a unit load device (ULD) type of transportation storage) ora conveyance device associated with the broadcasting node (such as aconveyor belt, a truck, a trailer, an aircraft, a train, and a deliveryvehicle).

As noted above, the processing unit of the master node device is adaptedand operative to instruct the communication interface broadcast ortransmit a command to the broadcasting other node. Such a command causesthat other node to change to a shortened format when broadcastingsubsequent advertising messages. In more detail, the command may causethe other node to broadcast the advertising message according to avariable broadcast format as the shortened format. In other words, theshortened format may vary and need not be a singular type of shortenedformat to use in all situations; instead, the format may be tailored forvarious degrees of compaction and identity specificity. For example,further embodiments explained in more detail below may have such avariable broadcast format including different types of shortened formats(such as a shortened global format, a shortened nested format, and ashortened local format) that may be separately deployed to help make formore efficient wireless node communications within the network.

In more detail, an embodiment of the shortened global format may includea global identifier of the broadcasting node (e.g., ID node 120 a)derived from the node device that detects the state change (e.g., masternode 110 a). The global identifier of the broadcasting node may furtherinclude a full identifier for the node device detecting the state changeand a shortened reference to the broadcasting node. For example, masternode 110 a may have a full identifier of M123456 while the broadcastingID node 120 a may have a full identifier of I123456. As such, anexemplary shortened global format for the broadcasting ID node 120 a maybe implemented as M1234546-1, which is a type of global identifier forID node 120 a derived from the master node detecting the state change(e.g., “M123456”) along with a shortened reference (e.g., the “-1”)representing ID node 120 a that indicates its relationship to masternode 110 a in a type of shorthand reference. Thus, the shortened globalformat may be helpful in situations where more compact communicationsare desired and there is the desire to avoid the communication overheadinvolved with contacting a backend server (e.g., server 100) todetermine the master node related to the broadcasting ID node.

The nested format may be helpful in situations where a hierarchy ofnodes is involved, such as when an ID node is placed within a ULD havingits own master node, and the ULD is placed within a vehicle having itsown master node. An embodiment of the shortened nested format mayinclude a nested identifier of the broadcasting node (e.g., ID node 120a) relative to the node device that detects the state change (e.g.,master node 110 a). The nested identifier may further include one ormore hierarchical references to higher level other nodes associated withthe broadcasting node. Such a nested identifier may indicate thebroadcasting node's relationships with the higher level other nodes andmay include a shortened reference to the broadcasting node. For example,an exemplary broadcasting ID node may use a full identifier of I123456while an exemplary ULD containing the ID node may use an identifier ofU123456 and an exemplary vehicle that maintains the ULD may use anidentifier of V123456. As such, an exemplary shortened nested format forthe broadcasting ID node may be implemented as VUI123456-1-1. Such anexemplary nested format has the broadcasting ID node referenced asUI123456-1 relative to the ULD, but as placed within the vehicle, thebroadcasting ID node is then able to use a nested type of referencing asVUI123456-1-1. Other ID nodes within the same ULD and vehicle may beshortened to VUI123456-1-2, VUI123456-1-3, and so forth where the “-2”and “-3” are shortened references to the other ID nodes in the same ULD.And broadcasting ID node within another ULD placed within the samevehicle may use a shortened nested format of VUI123456-2-1, where the“-2” indicates a shortened reference to the other ULD. Thus, such anexemplary shortened nested format for a broadcasting node allows theformat itself to indicate where the node was when it was renamed, whichavoids the communication overhead involved with contacting the backendserver to determine such information. This may provide the advantage ofa quicker responsiveness when the system needs to generate and transmitalert types of communications (as opposed to simply tracking types ofcommunications).

The shortened local format may be helpful in situations that are highlycontained and use of the shortened local format need only make sense toone node (e.g., master node 110 a that detected the change but that mayhave no other master nodes near it). An exemplary embodiment of theshortened local format may include a local identifier of thebroadcasting node (e.g., ID node 120 a) derived from an abbreviated nodereference for the node device detecting the state change (e.g., masternode 110 a). More specifically, the abbreviated node reference for thenode device detecting the state change may include a collapsed referenceto that node device and a shortened reference to the broadcasting node.In the example where the broadcasting ID node 120 a uses an identifierof I123456, an example of the shortened local format to be used by thatbroadcasting ID node may be M1-1, which is derived from an abbreviatednode reference to the master node 110 a (i.e., M123456) that detectedthe state change. As such, the “M1” in the example is a collapsedreference to the M123456 full identifier of the master node 110 adetecting the state change, while the “-1” is a shortened reference tothe broadcasting ID node 120 a. Thus, using M1-1 allows for a greaterdegree of format compaction but at the expense of ease ofidentification.

And while such types of shortened formats may be deployed by thebroadcasting node at the direction and control of the master node, afurther embodiment of such a master node device may have the nodeprocessing unit in the master node being further adapted and operativeto instruct the broadcasting node to alter the shortened format of theadvertising message back to the first format when the master nodedetects at least one further state change of the broadcasting node (suchas when ID node 120 a is detected to be at the end of conveyor system9805 and transitioning to moving while off the conveyor belt 9800 asshown in FIG. 98C).

FIG. 100 is a flow diagram illustrating an exemplary method for adaptivenode communication within a wireless node network having at least amaster node and an ID node in accordance with an embodiment from theoperational perspective of the master node device that controls how thebroadcasting ID node changes advertising message formats. Referring nowto FIG. 100, method 10000 begins at step 10005 where the master nodescans for an advertising message being broadcast by an ID node where themessage uses a first format. For example, as shown in FIG. 98A, masternode 110 a may be scanning for an advertising message broadcast by IDnode 120 a where the message uses a full format as shown in FIGS. 6-7.

At step 10010, method 10000 continues by detecting such an advertisingmessage. If no advertising message is detected, step 10010 has method10000 continuing to scan in step 10005. However, if such an advertisingmessage is detected in step 10010, method 10000 proceeds to step 10015where the master node detects a state change relative to the ID node.The state change is associated with a changed relative environment ofthe ID node. In one embodiment, the changed relative environment may bea change in a node density near the ID node. In another embodiment, thechanged relative environment may be a change in a movement aspect of theID node. More specifically, the change in the movement aspect of the IDnode may reflect that the ID node is substantially stationary relativeto a proximate structure (which may be moving while being substantiallystationary relative to the ID node). An exemplary proximate structuremay implemented by a package containing device for the ID node (such asa facility, a room, a bin, a container, a pallet, and a unit load device(ULD) type of transportation storage) or a conveyance device associatedwith the ID node (such as a conveyor belt, a truck, a trailer, anaircraft, a train, and a delivery vehicle).

If a state change is not detected at step 10015, step 10015 returns tostep 10005 to keep scanning. However, if such a state change isdetected, step 10015 proceeds to step 10020 where the master nodeinstructs the ID node to alter the first format of the advertisingmessage to a shortened format, which comprises an identifier for the IDnode that is derived from the changed relative environment of the IDnode. In a more detailed embodiment, the instructing step may beaccomplished when the master node transmits a control or command messageto the ID node, wherein the control or command message causes the IDnode to broadcast the advertising message according to a variablebroadcast format as the shortened format.

In an embodiment of method 10000, such a variable broadcast format maybe at least one of a shortened global format, a shortened nested format,and a shortened local format. In more detail, an embodiment of method10000 may use an exemplary shortened global format having a globalidentifier of the ID node derived from the master node detecting thestate change. The global identifier of the ID node may further comprisea full identifier for the master node detecting the state change and ashortened reference to the ID node.

Another embodiment of method 10000 may use an exemplary shortened nestedformat having a nested identifier of the ID node, where the nestedidentifier includes hierarchical references to higher level nodesassociated with the ID node. The nested identifier may also indicate theID node relationships with the higher level nodes, and may furthercomprise a shortened reference to the ID node.

Still another embodiment of method 10000 may use an exemplary shortenedlocal format having a local identifier of the ID node derived from anabbreviated node reference for the master node detecting the statechange. Further, the abbreviated node reference for the master nodedetecting the state change may comprise a collapsed reference to themaster node and a shortened reference to the ID node.

And in a further embodiment, method 10000 also includes instructing, bythe master node, the ID node to alter the shortened format of theadvertising message back to the first format when the master nodedetects at least one further state change of the ID node.

Those skilled in the art will appreciate that method 10000 as disclosedand explained above in various embodiments may be implemented on a node(such as exemplary master node 110 a as illustrated in FIGS. 98A-98C)running one or more parts of a master control and management code (suchas an exemplary adaptive messaging program code section implemented aspart of master control and management code 425) to implement any of theabove described functionality. Such code may be stored on anon-transitory computer-readable medium (such as memory storage 415 inexemplary master node 110 a). Thus, when executing such code, aprocessing unit of the node (such as unit 400) may be operative toperform the method and various steps as disclosed in the variousembodiments described above.

Enhanced Energy Management Aspects

Context Adjustment of Output Power

In some embodiments, the ability to adaptively adjust a node'sbroadcasting or advertising signal power may have certain advantages andparticular uses during operations of a wireless node network. FIGS.45A-45C are collectively a series of diagrams illustrating an exampleenvironment where a node is located in and may move between areas havingdifferent operating node densities and adaptively adjust node power inaccordance with an embodiment of the invention. Referring now to FIG. 45A, server 100 and master node 4500 are deployed as part of an exemplarywireless node network. Master node 4500 is illustrated to be incommunication with server 100 (such as through a second communicationinterface (e.g., medium/long range communication interface 485 forexemplary master node 110 a). While FIG. 45A-45C do not expressly showlines between the various nodes, those skilled in the art willappreciate that each of the nodes (e.g., master node 4500 and ID nodes4520 a-4520 g) have the capacity to communicate with each over and formassociations over short-range communication interfaces, such as aBluetooth® interface. The server 100 (with relayed commands by masternode 4500) or the master node without direction from sever 100 areoperative to fix an output power setting of any of ID node 4520 a-4520 gand be able to update that level depending on the circumstances. Whilenot shown in FIGS. 45A-45C, server 100 may, in other embodiments, haverelayed commands through one or more other master nodes so that theserver 100 is operative to fix an output power setting of any ID node ormaster node. And likewise, master node 4500 without direction from sever100 may be operative to fix an output power setting of any other masternode in the network.

As shown in FIG. 45A, ID nodes 4520 a-4520 g are located in twodifferent areas. Specifically, ID nodes 4520 a-4520 e are located withina first area 4505 while ID nodes 4520 f and 4520 g are located within asecond area. In one example, the first area 4505 may be a storagefacility, room, vehicle, container, or other bounded area. The secondarea 4510 may also be a storage facility, room, vehicle, container, orother bounded area. In a particular example, the first area 4505 is astorage room where packages and their related ID nodes are temporarilystored as the items in the packages are being shipped. The second area,in this particular example, is a sorting facility having a conveyorsystem at a particular point 4515 (such an entry point to the conveyorsystem) within the area 4510.

In a general embodiment, when a node passes a certain point (such anexit point of the first area 4505), the output power level beingbroadcast from the node may be changed depending upon a detected ordetermined change in the operating node density in the next area (or, insome embodiments, an anticipated next area).

In the example of FIG. 45A, one of the ID nodes (ID node 4520 a) isgoing to be moved from the first area 4505 to the second area 4510. IDnode 4520 a is initially located in the first area 4505, which has adensity of 4 other nodes operating within that area (e.g., ID nodes 4520b-4520 e). In contrast, the second area 4510 has 2 other nodes operatingwithin that second area (e.g., ID nodes 4520 f and 4520 g). As shown inFIG. 45B, ID node 4520 a has moved from the first area 4505 to thesecond area 4510 (more specifically, to a designated entry point 4515 ofthe conveyor system). With the second area 410 having an operating nodedensity less than the first area 4505, either server 100 or master node4500 may adapt the output power setting of ID node 4520 a to correspondwith the reduced operating node density, and update the output powersetting on ID node to a higher power level.

FIG. 46 is a flow diagram illustrating an exemplary method for adaptiveadjustment of node power level in a wireless node network depending uponoperating node densities when a node (such as ID node 4250 a) moves to anew area in accordance with an embodiment of the invention. Theembodiment with exemplary method 4600 is explained in terms of actionsby a server, but in light of the discussion above regarding FIG. 45A,those skilled in the art will further appreciate that such operationalsteps may also be performed, in another embodiment, by a master nodewithout direction of the server.

Referring now to FIG. 46, method 4600 begins with the server fixing anoutput power setting on a first of the nodes to a first power level whenthe first node is located in a first area where the first power levelcorresponds to a density of the nodes operating within the first area.In more detail, the first power level may correspond to a density of thescanning nodes operating within the first area. In the example of FIG.45A, server 100 may fix the output power setting on ID node 4520 a (viarelayed commands by master node 4500) to a low power level given theoperational node density in the first area 4505 is currently 4 nodes inthat area.

At step 4610, the server detects if the first node has moved to a secondarea. For example, server 100 may receive updated location data frommaster node 4500 that indicates ID node 4520 a is moving towards and nowinto second area 4510. In one embodiment, detecting may include trackingthe location of the first node as the first node moves from within thefirst area to within the second area, and determining when the locationof the first node has moved to within the second area.

In another embodiment, detecting by the server in step 4610 may bedetecting if the first node is anticipated to be moving from the firstarea to the second area. In other words, the server may anticipatemovement of the first node and detect an anticipated movement of thefirst node from the first area to the second area. In more detail, theserver may detect if the first node is anticipated to be moving from thefirst area to the second area by accessing context data related to anexpected transit path of the first node. In another embodiment, method4600 may also have the server predicting at least a portion of apredicted path for the first node, where the portion of the predictedpath includes the expected transit path of the first node from the firstarea to the second area.

At step 4615, the server adapts the output power setting on the firstnode to a second power level when the first node is located in thesecond area. The second power level corresponds to a density of thenodes operating within the second area. Thus, a change in operating nodedensity between the two areas can be accommodated with the adaptedoutput power setting on the first node. For example, the second powerlevel may be higher than the first power level when the density of thenodes operating within the second area is less than the density of thenodes operating within the first area. Likewise, the second power levelmay be lower than the first power level when the density of the nodesoperating within the second area is greater than the density of thenodes operating within the first area.

In a more detailed embodiment, the adapting step may have the serveradapting the output power setting on the first node to the second powerlevel when the first node is passing a point in the second area, such asan entry point of a conveyor system disposed within the second area. Thepoint may be a designated point or an anticipated point in differentembodiments. In the example of FIG. 45B, ID node 4520 a has moved withinsecond area 4510 and is passing the designated conveyor system entrypoint 4515 within second area 4510. As such, server 100 may adapt theoutput power setting on ID node 4520 a to a different power level basedupon the different operational node density within second area 4510.

In a further embodiment, method 4600 may have the server accessingcontext data related to the designated point in the second area toanticipate a density of the nodes expected to be operating within aproximate environment of the designated point, and may have the serverupdating the output power setting on the first node to a third powerlevel when the server detects the node is approaching the designatedpoint in the second area. In this embodiment, the third power level maycorrespond to the density of the nodes expected to be operating withinthe proximate environment of the designated point, which may bedifferent than simply the nodes operating within the second area.

In yet another embodiment, method 4600 may also have a second node withits output power setting adapted but in this situation the second nodecan do this based upon shared data from the first node. In more detail,method 4600 may further comprise adapting, by a second of the nodes, anoutput power setting on the second node to the second power level basedupon shared data received by the second node from the first node. Moreparticularly, the first node has its output power setting adapted andchanged to the second power level as recited in method 4600 but thenshares that second power level as a type of shared data with the secondnode. Here, if the server knows the second node is with the first node(e.g., traveling together as part of a multi-piece shipment, moving onthe same conveyor belt system in proximity to each other, etc.), theability to share the power level information allows for more efficientwireless node network operations.

In still another embodiment, the method 4600 may be implemented asperformed by a mobile master node instead of a server. In other words,an exemplary mobile master node in such an embodiment can self-adapt itsoutput power setting without requiring direction from the server. Inmore detail, the exemplary method is similar to that set forth above inmethod 4600 except that the first of the node perform each of the stepsand the first node may be a mobile master node. In such an embodiment,context data related to the expected transit path of the mobile masternode may be pre-loaded in the memory storage of the mobile master node.

Those skilled in the art will appreciate that method 4600 as disclosedand explained above in various embodiments may be implemented on anetwork device, such as exemplary server 100 as illustrated in FIG. 5 oran exemplary master node as illustrated in FIG. 4 (or master node 4500illustrated in FIGS. 45A-45C), running one or more parts of a controland management code (such as code 425 for a master node device or code525 for a server device) to implement any of the above describedfunctionality. Such code may be stored on a non-transitorycomputer-readable medium (such as memory storage 415 within an exemplarymaster node or memory storage 515 within an exemplary server). Thus,when executing such code, a processing unit (such as unit 400 within amaster node or unit 500 within a server) may be operative to performoperations or steps from the exemplary methods disclosed above,including method 4600 and variations of that method.

In yet another embodiment, an apparatus (such as a server or masternode) is described for adaptive adjustment of node power level in awireless node network. The apparatus comprises a processing unit and amemory coupled to the processing unit. The memory maintains code forexecution by the processing unit (such as code 425 or code 525) andoperational node density information related to a first area and asecond area (such as areas 4505 and 4510 illustrated in FIG. 45A-45C).The apparatus further comprises a communication interface coupled to theprocessing unit. The communication interface operates to communicatewith at least a first of a plurality of nodes in the network.

The processing unit of the apparatus, when executing the code maintainedon the memory, is operative to perform particular steps and operationssimilar to those explained above with respect to the various embodimentsof method 4600. In particular, the processing unit is operative to fixan output power setting on a first of the nodes to a first power levelwhen the first node is located in a first area, where the first powerlevel corresponds to a density of the nodes operating within the firstarea. This may be accomplished by sending a message over thecommunication interface to the first node as an instruction to fix theoutput power setting of the first node to the first power level. Theprocessing unit is then operative to detect if the first node has movedto a second area. In one example, this may be accomplished by having thenode processing unit being operative to track the location of the firstnode as the first node moves from within the first area to within thesecond area, and determine when the location of the first node has movedto within the second area.

In another example, the processing unit may be further operative todetect by being operative to detect if the first node is anticipated tobe moving from the first area to the second area. In more detail, thememory may maintain context data related to an expected transit path ofthe first node, and the processing unit may be further operative todetect if the first node is anticipated to be moving from the first areato the second area by being operative to access the context data on thememory, and using the context data to determine if the first node isanticipated to be moving from the first area to the second area.

When the first node is located in the second area, the processing unitis operative to adapt the output power setting to a second power level,which corresponds to a density of the nodes operating within the secondarea. In one example, the second power level may be higher than thefirst power level when the density of the nodes operating within thesecond area is less than the density of the nodes operating within thefirst area. In another example, the second power level may be lower thanthe first power level when the density of the nodes operating within thesecond area is greater than the density of the nodes operating withinthe first area.

In another embodiment, the processing unit may be operative to adapt byadapting the output power setting on the first node to the second powerlevel when the first node is passing a designated point in the secondarea. More specifically, in this other embodiment, the memory maycontain context data related to the designated point in the second area,and the processing unit may be further operative to access the contextdata to anticipate a density of the nodes expected to be operatingwithin a proximate environment of the designated point, and then updatethe output power setting on the first node to a third power level whenthe server detects the node is approaching the designated point in thesecond area, the third power level corresponding to the density of thenodes expected to be operating within the proximate environment of thedesignated point.

The processing unit is then operative to transmit a message over thecommunication interface to the first node to update the output powersetting on the first node to the second power level.

In another embodiment, the processing unit of the apparatus may also beoperative to predict at least a portion of a predicted path for thefirst node, wherein the at least portion of the predicted path comprisesthe expected transit path of the first node from the first area to thesecond area.

Thus, embodiments may adaptively adjust a node power level via theoutput power level broadcast from the node depending upon a detected ordetermined change in the operating node density in the next area (or, insome embodiments, an anticipated next area).

Proximity Adjustment of Output Power

Other embodiments may adaptively adjust a node power level via theoutput power level broadcast from the node depending upon whether athreshold number of other nodes are operating near or proximate to thefirst node or whether a threshold signal strength level is detected nearthe first node. Thus, such a threshold may be set relative to the numberof nodes or signal strength level detected as a measure of crowded nodeoperations.

Such a threshold may be set by the server as a type of context data,which could depend upon the contextual environment (e.g., a facility inwhich the first node is operating, a layout of the facility, machinerywithin the facility, RF signal degradation information about thesurrounding environment, etc.). For example, when it is detected ordetermined that a lot of ID nodes are in a room (via numbers of nodes orsignal strength levels), the power of one or more of the ID nodes can bedropped down to eliminate excess transmissions and/or noise, which mayallow the nodes to better communicate and locate each other withenhanced granularity.

Looking back at FIG. 45B, ID node 4520 a finds itself within second area4510 and with two other ID nodes (e.g., ID nodes 4520 f and 4520 g)operating near ID node 4520 a. In this situation, the transmissions andnoise emitting from the nodes may be tolerable such that an output powersetting of ID node 4520 a may be originally set as a medium level.However, over time, ID nodes 4520 b-4520 d may also move from the firstarea 4505 to the second area 4510, as illustrated in FIG. 45C. As aresult and referring to FIG. 45C, ID node 4520 a now finds itself having5 nodes operating near it. If the server 100 set the threshold (underthe contextual circumstances) to 4, then the number of nodes operatingnear or proximate to ID node 4520 a exceeds the threshold and the outputpower setting is changed to an adapted level (e.g., a low RF outputpower level), which is different from the original level (e.g., a mediumRF output power level). Those skilled in the art will appreciate thatwhile a low or medium level is disclosed as exemplary output powersettings, an embodiment may have a specific power level and may changein increments relative to the extent the number of other nodes operatingproximate ID node 4520 exceed the threshold. The ability to flexibly setthe threshold by the server and the ability to adaptively set the outputpower settings to levels that make sense in the particular context ofthe node of interest may further enhance node operations in an exemplaryembodiment of the wireless node network.

As previously noted, the server 100 (with relayed commands by masternode 4500) or the master node without direction from sever 100 areoperative to fix or adapt an output power setting of any of ID node 4520a-4520 g and be able to update that level depending on thecircumstances. While not shown in FIGS. 45A-45C, server 100 may, inother embodiments, have relayed commands through one or more othermaster nodes so that the server 100 is operative to fix or adapt anoutput power setting of any ID node or master node. And likewise, masternode 4500 without direction from sever 100 may be operative to fix anoutput power setting of any other master node in the network.

FIG. 47 is a flow diagram illustrating an exemplary method for adaptiveadjustment of node power level in a wireless node network depending upona threshold of operating nodes within a given area in accordance with anembodiment of the invention. The embodiment with exemplary method 4700is explained in terms of actions by a server, but in light of thediscussion above regarding FIGS. 45B-45C, those skilled in the art willfurther appreciate that such operational steps may also be performed, inanother embodiment, by a master node without direction of the server.

Referring now to FIG. 47, method 4700 begins at step 4705 with theserver detecting if a number of other nodes operating proximate a firstof the nodes exceeds a threshold. In one embodiment, the number of othernodes operating proximate the first node may comprise a number of othernodes operating within a first communication area around the first node.For example, the first communication area around the first node may bedefined by a transmission range around the first node or by a receptionrange from the first node. In another example, the first communicationarea around the first node may be defined by a first transmission rangearound the first node adjusted based upon context data related to anenvironment proximate the first node. Exemplary context data, such ascontext data 560, may include information on anticipated signaldegradation for a similar environment to the environment proximate thefirst node (e.g., a type of RF data 587).

At step 4710, method 4700 concludes with the server adapting an outputpower setting on the first node from an original level to an adaptedlevel when the number of other nodes operating proximate the first nodeexceeds the threshold. In one embodiment, the adapted level may comprisean RF output signal level that is decreased relative to the originallevel. For example, the decreased RF output signal level of the adaptedlevel may be based upon or commensurate with the extent the number ofother nodes operating proximate the first node exceeds the threshold.Thus, if a relatively large number of nodes are operating proximate thefirst and that greatly exceeds the threshold, then the adapted level maybe significantly decreased. However, if the number of nodes operatingproximate the first only barely exceeds the threshold, then the adaptedlevel may only be slightly decreased. Those skilled in the art willappreciate that the amount of any decrease and setting of any thresholdwill be subject to the details of the implementation and intendedenvironment where the node is expected to operate within.

Method 4700, in a further embodiment, may also include altering theoutput power setting to the original level when the server detects thenumber of other nodes operating proximate the first node no longerexceeds the threshold. Thus, the adaptive nature of an embodiment maycompensate for going over the threshold as well as coming back under thethreshold so as to better enhance node communications and the ability tolocate a node within an exemplary wireless node network.

Those skilled in the art will appreciate that method 4700 as disclosedand explained above in various embodiments may be implemented on anetwork device, such as exemplary server 100 as illustrated in FIG. 5 oran exemplary master node as illustrated in FIG. 4 (or master node 4500illustrated in FIGS. 45B-45C), running one or more parts of a controland management code (such as code 425 for a master node device or code525 for a server device) to implement any of the above describedfunctionality. Such code may be stored on a non-transitorycomputer-readable medium (such as memory storage 415 within an exemplarymaster node or memory storage 515 within an exemplary server). Thus,when executing such code, a processing unit (such as unit 400 within amaster node or unit 500 within a server) may be operative to performoperations or steps from the exemplary methods disclosed above,including method 4700 and variations of that method.

In another embodiment, another exemplary method that may be implementedby a server is described for adaptive adjustment of node power level ina wireless node network having a plurality of nodes and a server. Themethod uses a threshold based upon signal strength level measured at thefirst node, rather than a number of nodes operating within an areaaround the first node. In particular, an embodiment of the method beginsby detecting, by the server, if a signal strength level near a first ofthe nodes exceeds a threshold. The method continues by adapting, by theserver, an output power setting on the first node from an original levelto an adapted level when the signal strength level near the first nodeexceeds the threshold.

Furthermore, the adapted level may comprise an RF output signal levelthat is decreased relative to the original level based upon the extentthe detected signal strength exceeds the threshold. And even further,the method may include altering the output power setting to the originallevel when the server detects the signal strength level no longerexceeds the threshold.

In still another embodiment, another exemplary method that may beimplemented by a server is described for adaptive adjustment of nodepower level in a wireless node network having a plurality of nodes and aserver. The method relies upon a location of the first node as acondition for adapting the output power setting of the node. Inparticular, an embodiment of the method begins by detecting, by theserver, if a first of the nodes is located in an RF restricted area. Themethod continues by adapting, by the server, an output power setting onthe first node from an original level to an adapted level when the firstnode is located in the RF restricted area. The method may includealtering the output power setting to the original level when the serverdetects the signal strength level no longer exceeds the threshold. Thus,a server apparatus may implement such a method related to operatingaround and within restricted RF areas (such as on an aircraft or inmedical facilities where RF interference is an issue).

In yet another embodiment, an apparatus (such as a server or masternode) is described for adaptive adjustment of node power level in awireless node network. The apparatus comprises a processing unit and amemory coupled to the processing unit. The memory maintains code forexecution by the processing unit (such as code 425 or code 525) andlocation data regarding the nodes. The apparatus further comprises acommunication interface coupled to the processing unit. Thecommunication interface operates to communicate with at least a first ofa plurality of nodes in the network.

The processing unit of the apparatus, when executing the code maintainedon the memory, is operative to perform particular steps and operationssimilar to those explained above with respect to the various embodimentsof method 4700. In particular, the processing unit is operative toaccess the location data on the memory, identify how many of the nodesare operating proximate the first node based upon the location data, andthen detect if the identified number of other nodes operating proximatethe first node exceeds a threshold. In one embodiment, the number ofother nodes operating proximate the first node may comprise a number ofother nodes operating within a first communication area around the firstnode. In one example, the first communication area around the first nodemay be defined by a transmission range around the first node or by areception range from the first node. In more detail, the firstcommunication area around the first node may be defined by a firsttransmission range around the first node adjusted based upon contextdata related to an environment proximate the first node. Such contextdata may, for example, include information on anticipated signaldegradation (e.g., RF data 587) for a similar environment to theenvironment proximate the first node.

The processing unit is then operative to adapt an output power settingon the first node from an original level to an adapted level when theidentified number of other nodes operating proximate the first nodeexceeds the threshold. In one embodiment, the adapted level comprises anRF output signal level that may be decreased relative to the originallevel based upon the extent the number of nodes operating proximate thefirst node exceeds the threshold.

In another embodiment of the apparatus, the processing unit may befurther operative to transmit a message to the first node to alter theoutput power setting to the original level when the number of nodesoperating proximate the first node no longer exceeds the threshold.

In a more specific embodiment, a master node is described for adaptiveadjustment of node power level in a wireless node network of a pluralityof other nodes and a server. The master node comprises a master nodeprocessing unit and a master node memory coupled to the processing unit.The master node memory maintains code (such as code 425) for executionby the master node processing unit and location data regarding the othernodes. The master node further comprises a first communication interfacecoupled to the master node processing unit and operative to communicatewith at least a first of the of other nodes in the network. And themaster node also comprises a second communication interface coupled tothe server.

The master node processing unit, when executing the code maintained onthe master node memory, is operative to perform particular steps andoperations similar to those explained above with respect to the variousembodiments of method 4700. In particular, the master node processingunit is operative to receive a threshold setting from the server overthe second communication interface, access the location data on themaster node memory, identify how many of the nodes are operatingproximate the first node based upon the location data, and then detectif the identified number of other nodes operating proximate the firstnode exceeds the threshold setting received from the server.

In one embodiment, the number of other nodes operating proximate thefirst node may comprise a number of other nodes operating within a firstcommunication area around the first node. In one example, the firstcommunication area around the first node may be defined by atransmission range around the first node. In more detail, the firstcommunication area around the first node may be defined by a firsttransmission range around the first node adjusted based upon contextdata related to an environment proximate the first node. Such contextdata may, for example, include information on anticipated signaldegradation (e.g., RF data 587) for a similar environment to theenvironment proximate the first node.

The master node processing unit is then operative to adapt an outputpower setting on the first node from an original level to an adaptedlevel when the identified number of other nodes operating proximate thefirst node exceeds the threshold. In one embodiment, the adapted levelcomprises an RF output signal level that may be decreased relative tothe original level based upon the extent the number of nodes operatingproximate the first node exceeds the threshold setting received from theserver.

In another embodiment of the apparatus, the processing unit may befurther operative to transmit a message to the first node to alter theoutput power setting to the original level when the number of nodesoperating proximate the first node no longer exceeds the thresholdsetting received from the server.

Power Profile Management

One of the advantageous aspects of certain embodiments may come from howa master node can adjust settings on the ID node, which cannotcommunicate directly with the server. In some embodiments, the masternode is able to accomplish adjusting a broadcast setting of an ID nodeusing a type of broadcast profile for the ID node. In general, a profilegenerally contains information that defines the behavior of the ID nodedevice. In one example, a broadcast profile (e.g., information stored asprofile data 330) may contain information that defines how an ID nodebroadcasts signals and communicates with other nodes.

Referring back to the exemplary embodiment shown in FIG. 34C, as ID node120 a approaches facility master node 3430, master node 3430 may detectan advertising signal from ID node 120 a when ID node 120 a is withinrange. After associating with the ID node 120 a, facility master node3430 is able to change or adjust a broadcast profile for ID node 120 aso that ID node 120 a behaves or communicates in a manner thatappropriate and dictated by master node 3430 (or via instructions sentfrom server 100 to facility master node 3430).

In another example, a node may be associated with structure, such as aULD or drop box receptacle. As such, the node would be aware ofcharacteristics of the structure (e.g., via context data about thestructure) and may have a predetermined value (e.g., a default value)for a broadcast setting (e.g., an RF transmission output power levelsetting) for nodes entering the structure. In such an example, theinterior space of the structure may be the interior of a commonly useddrop box receptacle. The node associated with the receptacle may detectan ID node approaching, associate with the approaching ID node, andadjust a current RF output power level to an updated (e.g., lower) RFoutput power level as the detected ID node enters the interior of thedrop box receptacle. In another embodiment, the adjustment to theupdated RF output power level may occur prior to entering the structure.This may be accomplished by modifying the broadcast profile for the nodeentering the structure so that, for example, the node causes lessdisruption within a confined interior of the structure. In somesituations, an ID node may have a default broadcast profile in memoryonboard (e.g., the information in profile data 330) to be used wheneverthe ID node is associated with certain structure (e.g., a ULD, drop boxreceptacle) or another node associated with such structure.

FIG. 52 is a flow diagram illustrating an exemplary method for adjustinga broadcast setting of a node in a wireless node network having a masternode and a server in accordance with an embodiment of the invention.Referring now to FIG. 52, method 5200 begins at step 5205 with themaster node detecting an advertising signal from the node. In oneembodiment, the node may be an ID node (such as ID node 120 a) capableof communicating directly with the master node but incapable ofcommunicating directly with the server in the wireless node network. Ina more detailed, such an ID node may have pre-staged context aware dataresiding on the node and be operative to self-adjust its broadcastsetting to an updated value based on the pre-staged context data.

At step 5210, method 5200 continues by establishing an activeassociation with the node. In one embodiment, the active association ofthe master node and the detected node may reflect a secure connectionbetween the master node and node. In this way, the master node maysecurely share information with the node.

At step 5215, method 5200 continues by determining an updated value forthe broadcast setting of the node. In a general embodiment, thebroadcast setting of the node is setting related to characteristicaspects of a signal (such as an advertising signal) broadcast from thenode. Examples of such a broadcast setting may include an RFtransmission output power level setting, a frequency setting, and atiming setting. In more detail, the RF transmission output power levelsetting may be a specific power level that may or may not be adjustedbased upon context data (e.g., signal degradation information generallystored as RF data). Likewise, a more detailed example may adjust thefrequency setting as a carrier frequency of the signal output from thenode or the interval frequency in how often the signal is transmittedfrom the node. Exemplary timing settings may include other types ofsettings related to the signal broadcast from the node, such as dutycycle settings, etc.

In one embodiment, the updated value for the broadcast setting may beaccessed on memory of the master node and determined by the master nodeitself (e.g., such as with adjustments made for context data). Inanother embodiment, the updated value for the broadcast setting may bereceived from the server and stored on the master node's memory.

At step 5220, method 5200 concludes by adjusting the broadcast settingof the node from a current value to the updated value. In oneembodiment, the updated value may be a predetermined value related to astructure, where the structure is associated with the master node. Inanother embodiment, the updated value is a default broadcast valuerelated to an interior of the structure, where the structure is ashipping container associated with the master node. Thus, when aparticular part of a structure (e.g., the interior of a ULD) has beencharacterized with a similar node, the system may predetermine that anode entering such a structure should have its broadcast profilemodified. For example, adjusting the broadcast setting of the node mayinvolve modifying the broadcast profile of the node, where the broadcastprofile defines the broadcast setting used when the node communicateswith the master node. An exemplary broadcast profile may includedifferent types of broadcast settings (e.g., RF transmission outputpower level setting, a frequency setting, a timing setting) that arerelied upon by the node when broadcasting signals.

Those skilled in the art will appreciate that method 5200 as disclosedand explained above in various embodiments may be implemented on amaster node, such as exemplary master node illustrated in FIG. 4,running one or more parts of a control and management code (such as code425 for a master node device) to implement any of the above describedfunctionality. Such code may be stored on a non-transitorycomputer-readable medium (such as memory storage 415 within an exemplarymaster node). Thus, when executing such code, a processing unit (such asunit 400 within a master node) may be operative to perform operations orsteps from the exemplary methods disclosed above, including method 5200and variations of that method.

In yet another embodiment, a master node is described for adjusting abroadcast setting of a node in a wireless node network. The master nodecomprises a processing unit and a memory coupled to the processing unit.The memory maintains code for execution by the processing unit (such ascode 425) and an updated value for the broadcast setting of the node.The master node further comprises a first communication interface and asecond communication interface, both of which are coupled to theprocessing unit. The first communication interface is operative tocommunicate with the node in the network, and the second communicationinterface is operative to communicate with a server in the network.

The processing unit of the master node, when executing the codemaintained on the memory, is operative to perform particular steps andoperations similar to those explained above with respect to variousembodiments of method 5200. In particular, the processing unit isoperative to detect that the first communication interface receives anadvertising signal from the node, establish an active association withthe node and store association data on the memory to reflect the activeassociation between the master node and the node, access the updatedvalue from the memory, and transmit a message to the node over the firstcommunication interface, the message instructing the node to adjust acurrent value of the broadcast setting of the node to the updated value.In one embodiment, the node may be an ID node operative to communicatedirectly with the master node over the first communication interface butincapable of communicating directly with the server. And in anotherembodiment, the processing unit may be further operative to receive theupdated value from the server over the second communication interface.

In still another embodiment of the master node, the processing unit maybe further operative to modify a broadcast profile of the node, wherethe broadcast profile defines the broadcast setting used when the nodecommunicates with the master node. The processing unit may then beoperative to transmit the message by being operative to transmitinformation to the node over the first communication interface, wherethe transmitting information reflects the modified broadcast profile.

Furthermore, those skilled in the art will recognize that exemplarynetwork components shown in FIG. 34C depict an exemplary interactivesystem involving server 100, master node 3430 and ID node 120 a wherethe system's master node 3430 is able to chance or adjust a broadcastprofile for ID node 120 a so that ID node 120 a behaves or communicatesin a manner that appropriate and dictated by master node 3430 (or viainstructions sent from server 100 to facility master node 3430) asdiscussed above. Additionally, the exemplary system embodiment shown inFIG. 34C may have the system components operate as described withrespect to method 5200 and variations of that method as explained inmore detail below.

Enhanced Power-Related Alerts

As most mobile components in an exemplary wireless node network have apower source, such as a battery, that runs down over time with normalusage, an embodiment of the network may find an exemplary network device(such as an ID node or mobile master node) in a situation where power isrunning low. In such an embodiment, a network device, such as an ID nodeor master node, may advantageously notify other network devices (and insome cases, the server) of their current location and that they arerunning low on power in order to help prevent network devicesunexpectedly and needlessly becoming inoperative due to lack of power.In general, the network device may send out an alert that its batteryneeds to be changed and its location.

As shown in FIG. 3, an exemplary ID node 120 a includes a battery 355,which is a type of power source. Similarly, as shown in FIG. 4, anexemplary master node 110 a may include a battery 470 (especially formobile master nodes). In one embodiment, the processing unit of therespective network device (such as processing unit 300 of ID node 120 aor processing unit 400 of master node 110 a) may have an ability todetect the power status of the device (e.g., a current voltage levelavailable across the terminals of the battery, within one of a range ofvoltages, etc.). In another embodiment, additional voltage detectioncircuitry may be incorporated as part of the power source or interfacingcircuitry between the power source and the processing unit such that theprocessing unit is able to receive an indication of the current powerstatus of the power source (and of the device given that the powersource provides power for the device). For example, an exemplaryprocessing unit 300 of an ID node may include buffer circuits that mayinterface with a voltage detection circuit, which is coupled to theoutput of the battery 355. The processing unit 300 may be operative touse its buffer circuitry and an output of the voltage detection circuitto detect a current power status of the battery.

With a detected power status, processing unit 300 may compare thatcurrent measurement with a threshold to determine an appropriateresponse. In one example, an exemplary threshold may be a designatedvoltage level. In another example, multiple thresholds may be employedwhere each time the current power status drops below a differentthreshold, a different type of enhanced power alert notification may bebroadcasted and elicit a different type of response from devices thatreceive the notification. For example, a node may have several differentthresholds—an initial “low” level threshold, a lower “urgent” levelthreshold, and an even lower “critical” level threshold. When the powersource on the node goes below each of these different thresholds,different alert levels may be assigned.

In a further embodiment, an exemplary threshold may be based uponcontext data. For example, a threshold may be based on how much isremaining of the anticipated shipment journey, generally referred to asa shipment journey status. Thus, if the context data indicates that anode is in the midst of being shipped and is only 25% into itsanticipated shipment journey, the threshold level may be higher than ifonly 10% of the anticipated shipment journey is left. In other words,when there is only 10% of the journey left, there is more comfort with alower detected power status than if the node is only 25% into thejourney and still has 75% of the journey (which, according to furthercontext data, may require operations well beyond a predicted point ofpower depletion).

In a more detailed example, the node may further respond by onlyperforming certain ones of prioritized functions or operations once thedetected power status is lower than a threshold. In other words, theexemplary node may be operative to prioritize operations as anappropriate response to when the detected power status is below athreshold level.

In general, an alert level may be assigned by the network devicereporting a low power situation. The alert level provides a generalmechanism by which to externally indicate the severity of a low powercondition on a particular network device. For example, a first alertlevel may be when the detected current power status is less than theinitial “low” threshold; a second alert level may be when the detectedcurrent power status is below the lower “urgent” level threshold; and athird alert level may be when the detected current power status is belowthe “critical” level threshold. Actions to be taken with a nodereporting such alert levels may depend on the contextual environment andlocation of the node.

Those skilled in the art will appreciate that the described embodimentsexplain an enhanced or improved way to notify other network componentswith an alert related to the node's power status. Such an enhancementfundamentally effects an improvement in the management technology of howto become aware of and to locate different nodes within the network asthey are deployed in business operations, such as logistics, shippingmanagement, and inventory management, when the nodes begin to lose powerand need assistance with varying degrees of urgency. The ability for anode to broadcast an improved power alert notification that involves acurrent power status and location of the node greatly enhancesapplications that use wireless node networks (e.g., technical fieldssuch as logistics, shipping management, inventory management, and thelike). In other words, the exemplary embodiments described herein withinterrelated operations between a reporting network device (such as anID node or battery powered master node) other nodes in the network,provide a type of specially-adapted system that enhances and improvesnode management operations in technical fields such as logistics,shipping management, inventory management, and the like where wirelessnodes may rely upon battery power.

FIG. 53 is a flow diagram illustrating an exemplary method for enhancedpower notification from an ID node in a wireless node network having amaster node and a server in accordance with an embodiment of theinvention. Those skilled in the art will appreciate that the generalsteps recited specific to actions taken by an ID node (i.e., a nodecapable of communicating directly with the master node but incapable ofcommunicating directly with the server) in this embodiment may besimilarly taken by a mobile master node (i.e., a node capable ofcommunicating directly with the server and separately communicating withan ID node) that is running low on power. Referring now to FIG. 53,method 5300 begins at step 5305 where the ID node detects a currentpower status for the ID node. In one embodiment, the power status may bea numeric voltage reading on the power source of the ID node. In anotherembodiment, the power status may be a qualitative range determination(such as one of multiple ranges of power for the power source on the IDnode).

At step 5310, method continues by determining a current location of theID node. In general, a location of the node may be relative to othernodes or structures or places, but may also be more precise, such as aset of coordinates (e.g., GPS coordinates identifying a location inthree dimensions). In one embodiment, the current location may be storedas location data on the ID node. In another embodiment, the currentlocation may be determined by the node (e.g., via location circuitry) orby requesting the node's a location from an associated node.

At step 5315, method 5300 concludes where the ID node broadcasts anenhanced power alert notification when the current power status of theID node is below a threshold. The enhanced power alert notification is amessage or signal that indicates that the current power status of the IDnode is below the threshold and includes the current location of the IDnode. In another embodiment, the enhanced power alert notification mayalso include a request for a replacement power source for the ID node.In still another embodiment, the enhanced power alert notification mayalso include a request to recharge an existing power source in the IDnode. In this way, the exemplary notification provides an identificationof the node issuing it along with relevant information about thenotification and the low power event/condition leading up to it.

In another embodiment, method 5300 may also include the step ofassigning an alert level based upon the current power status for the IDnode, and broadcasting the enhanced power alert notification to includeat least the current location of the ID node and the assigned alertlevel as a more detailed way to enhance the notification function. Theassigned alert level may instruct the master node to take a responsiveaction when the master node receives the broadcasted enhanced poweralert notification, where the responsive action depends on the assignedalert level.

In more detail, the assigned alert level part of the enhanced poweralert notification may instruct the master node to notify the server(e.g., notify the server about the current location of the ID node andthe assigned alert level) after the master node receives the broadcastedenhanced power alert notification.

And in a further embodiment, method 5300 may also include receiving, bythe ID node, an alert response from the master node, where the alertresponse changes a broadcast setting for the ID node. For example, amaster node may receive the broadcasted enhanced power alertnotification from the reporting ID node, and be instructed by the serverto have the reporting ID node change how often the node broadcasts givenits location and where the server expects the reporting node to beheaded (e.g., a storage facility in transit where the battery can bereplaced).

In another embodiment, method 5300 may also include prioritizing one ormore operations within the ID node to conserve power when the currentpower status of the ID node is below the threshold. Thus, the ID nodemay intelligently manage its onboard operations while also alertingother network devices about its power status.

Further still, an embodiment of method 5300 may establish the thresholdas a value based upon context data related to the ID node. In moredetail, the threshold may be a value based upon context data related toa shipment journey status for the node. Thus, context data may informthe ID node about where it is along its shipment journey, which can beused to dynamically determine a contextually appropriate value for thethreshold and when the ID node should be issuing such enhanced poweralert notifications.

Those skilled in the art will appreciate that method 5300 as disclosedand explained above in various embodiments may be implemented on an IDnode, such as exemplary ID node illustrated in FIG. 3, running one ormore parts of a control and management code (such as code 325 for an IDnode type of network device) to implement any of the above describedfunctionality. Such code may be stored on a non-transitorycomputer-readable medium (such as memory storage 315 within an exemplaryID node type of network device). Thus, when executing such code, aprocessing unit (such as unit 300 within an ID node) may be operative toperform operations or steps from the exemplary methods disclosed above,including method 5300 and variations of that method. In other words, aprocessing unit within the respective network element (e.g., an ID node)may be specially-adapted by executing such code, which then causes thenode's processing unit to function as an application-specific type ofhardware device with specific interactions with other elements of thenetwork (e.g., the master node and the server) when implementingenhanced power notification as described by the exemplary methodsdisclosed above, including method 5300 and variations of that method.

Likewise, those skilled in the art will further appreciate that anotherembodiment of method 5300 as disclosed and explained above may beimplemented on a mobile master node instead of an ID node. Both types ofnetwork devices use power sources of a finite nature, and thus anexemplary mobile master node may also take advantage of such a methodfor enhanced power notification from the master node when the masternode's power source becomes low.

In yet another embodiment, a network device (such as an ID node or amaster node) capable of enhanced power notification is described. Thenetwork device comprises a processing unit and a memory coupled to theprocessing unit. The memory maintains code for execution by theprocessing unit (such as code 425 if implemented as a master node orcode 325 if implemented as an ID node). The network device furthercomprises a short-range communication interface coupled to theprocessing unit and operative to communicate with another network devicein the network. And the network devices further comprises a power sourcecoupled to the processing unit and providing power for the networkdevice.

The processing unit of the network device, when executing the codemaintained on the memory, is operative to perform particular steps andoperations similar to those explained above with respect to variousembodiments of method 5300. In particular, the processing unit isoperative to detect a current power status of the power source,determine a current location of the network device, and broadcast anenhanced power alert notification over the short-range communicationinterface when the current power status of the power source is below athreshold. The enhanced power alert notification indicates that thecurrent power status of the power source is below the threshold andincluding the current location of the network device.

In one embodiment, the processing unit of the network device isoperative to communicate directly with a master node in the wirelessnode network over the short-range communication interface but unable tocommunicate directly with a server in the wireless node network.

In another embodiment, the network device may also include alonger-range communication interface coupled to the processing unit andbe operative to communicate with a server in the wireless node network.In more detail, the network device may further include locationcircuitry (such as a GPS chip) coupled to the processing unit andoperative to receive at least one location signal and provide thecurrent location of the network device to the processing unit as part ofdetermining the current location of the network device. In still anotherembodiment, the processing unit of the network device may be operativeto determine the current location of the network device by accessingdata maintained on the memory, where the data represents the currentlocation of the network device.

Furthermore, those skilled in the art will recognize that exemplarynetwork components shown in FIGS. 1 and 2 depict an exemplaryinteractive system with network elements, such as an ID node 120 a,master node 110 a, and server 100, that collectively implement enhancedpower notification as described above in more detail. Additionally, suchan exemplary system embodiment may have the ID node (as well as themaster node and server) operate as described with respect to method 5300and variations of that method as explained in more detail below.

Enhanced Logistics Operations

Magnetically Altering Node Operation

A variety of enhanced embodiments may be achieved with a magneticallyactuated node. While nodes communicate through their respectivecommunication interfaces via conventional electronic (or electromagneticwaves) signals (such as with Bluetooth® enabled communications or NFCfor short range communications and WiFi for medium/longer rangecommunications) another medium of control and communication for a noderelates to magnetic fields and, more specifically, to detecting a changein a magnetic field in the proximate environment of a node. In variousembodiments disclosed below, a magnetic switch (e.g., a reed switch) maybe deployed as part of a node's peripheral circuitry and may be used toalter the operation of a management function for the node.

FIG. 3, as described above, shows magnetic switch 365 being part of or,in some instances, integrated into an ID node. FIGS. 48A-48C, 49A-49B,and 50A-50B show example configurations of a wireless node networkdeploying different embodiments of a magnetically actuated node.Referring now to FIG. 48A, the exemplary network includes server 100,master node 110 a, and ID node 120 a. Server 100 is in communicationwith master node 110 a. And master 110 a operates at a middle level ofthe network in communication with ID node 120 a (typically on a separatecommunication interface than the communication path to server 100). Asshown in FIG. 48A, ID node 120 a includes a magnetic switch 365, whichenables the ID node 120 a (along with programming in code 325 of ID node120 a) to magnetically alter an operation of ID node 120 a as explainedin more detail in the below embodiments.

In FIG. 48A, magnetic switch 365 in ID node 120 a is exposed to anddetects a magnetic field 4805 from a magnetic field source 4800. Whenexposed to such a magnetic field 4805, magnetic switch 365 alters itsswitch configuration from either open to closed or closed to open.Various embodiments of a magnetic switch 365 may be employed withvarious poles and various throws depending on the particular needs ofthe implementation. For example, magnetic switch 365 may be a simplesingle pole, single throw switch that closes when exposed to a magneticfield. Other examples of a magnetic switch may be more complex withmultiple inputs and outputs (multiplexer like configuration), but stillcontrolled via a change in magnetic field.

In FIG. 48B, ID node 120 a moves away from magnetic field source 4800and the magnetic fields 4805 emanating from the source. At a certaindistance away from source 4805, magnetic switch 365 in ID node 120 maydetect that the magnetic field in the proximate environment of ID node120 is no longer the same and has changed compared to the situationillustrated in FIG. 48A. In other words, with a detected change inmagnetic field (e.g., the substantial absence of field 4805), magneticswitch 365 actuates to a different state (e.g., from open to closed orvice versa) such that the ID node 120 a may alter its operation inresponse. For example, when magnetic switch 365 changes states, this maycause a signal to be sent to the processing unit 300 of ID node 120 a sothat the ID node 120 a may take action and alter its operation inresponse. Those skilled in the art will appreciate that, as shown inFIG. 48C, essentially the same response may be achieved in the ID node120 a if instead of moving the ID node 120 a from a stationary magneticfield source 4800, and an example configuration moves the source 4800relative to a stationary ID node 120 a.

In a more detailed application embodiment, a customer may be ready toship a package. The package may include a related ID node, or the IDnode may be added to the package when the customer packages the item forshipment. In this embodiment, the ID node may have a magnet related toit that is initially held in a position that is next to or at leastsubstantially proximate to the ID node so that the magnetic fieldgenerated by the magnet keeps the ID node in a low or unpowered state.When the customer desires to the ship the item and use the ID node aspart of the packaged shipment of the item, the customer would remove themagnet, which can then energize and power the ID node. In a furtherembodiment, the removed magnet may be stored. Further, anotherembodiment may have the customer place and human/machine readable labelor node identifier that indicates the packaged item is node-enabled (bya human reading the label or a scanner analyzing the label).

When the change in magnetic field is detected, for example by magneticswitch 365, embodiments may alter various types of management functionsof ID node 120 a. In general, a management function of ID node 120 is afunction that impacts the operation of the node. Exemplary managementfunctions of a node may include, but are not limited to, changing apower condition of the node (e.g., powering up the node, changing to alower energy consumption mode, overriding a power setting previouslyestablished by a master node or server), transmitting an alert (e.g.,notifying other nodes of the ID node's location, sending out a securityalert related to an object associated with the ID node), changingassociation data related to the node, and logging usage information forthe node, an item related to the node, or a moveable object separatefrom the node.

In more detail, referring to FIG. 49A, ID node 120 a is shown being heldin place by placement support 4900, which may in one example be aholster that holds the ID node 120 a in place but may allow the ID node120 a to be easily moved off or out of placement support 4900 whendesired. As shown in the example of FIG. 49A, placement support 4900includes a magnetic field source 4905 that emanates a magnetic field4910. When ID node 120 a is moved out of placement support 4900, asshown in FIG. 49B, magnetic switch 365 is no longer exposed and candetect magnetic field 4910 and, as a result, changes states, which maycause a signal to be sent to the processing unit 300 of ID node 120 a.And in response, a management function of ID node 120 a may be altered.

Another example configuration is shown in FIG. 50A, where ID node 5110 ais part of placement support 5005, which supports object 5000. Object5000 includes or has attached to it a magnetic field source 5010emanating a magnetic field 5105. Thus, object 5000 is an example of amovable magnetic object relative to ID node enabled structure, such asplacement support 5005. Those skilled in the art will appreciate thatother types of structure may be used to house or hold an ID node near amoveable magnetic object. Likewise, those skilled in the art willappreciate that other types of structure may be used to house or hold amagnetic source relative to an ID node.

In the example of FIG. 50A, a magnetic switch within ID node 5110 a maybe exposed to the magnetic field 5105. However, when the object 5000 ismoved from placement support 5005 and the magnetic switch in ID node5110 a (in placement support 5005) is no longer exposed to the magneticfield 5105, this change in magnetic fields causes a change in state forthe magnetic switch and a responsive altering of a management functionin ID node 5110 a.

FIG. 51 is a flow diagram illustrating an exemplary method formagnetically altering an operation of a node in a wireless node networkhaving a master node and a server in accordance with an embodiment ofthe invention. Referring now to FIG. 51, method 5100 begins at step 5105the node detecting one or more magnetic field changes in a proximateenvironment of the node. In one example, the one or more magnetic fieldchanges reflect an increase in a magnetic field in the proximateenvironment to the node. In another example, the one or more magneticfield changes reflect a decrease in a magnetic field in the proximateenvironment to the node. For example, with reference to FIG. 49A-49B,the change in magnetic fields in the proximate environment to ID node120 a would be an increase when ID node 120 a is moved off, out of, oraway from placement support 4900 (which includes a magnetic field source4905 in it). In an example where placement support 4900 is a holster orother type of holder and ID node 120 a is part of an item placed in andout of the holster, the fields would be increasing when placing the itemand ID node 120 a in the holster 4900 but decreasing when removing theitem and ID node 120 a from the holster 4900.

In one embodiment, the detecting step may further comprise sensing analtered configuration of a magnetic switch integrated within the node.For example, magnetic switch 365 may be in one state (e.g., open) whenexposed to magnetic field 4910 in FIG. 49A, but may shift to be inanother state (e.g., closed) when that magnetic field 4910 is decreasedwhen ID node 120 a is moved from placement support 4900 in FIG. 49B. Theresulting change in circuit state for magnetic switch 365 (or moregenerally a different configuration of the switch) may be sensed by theprocessing unit on ID node 120 a, which can then react and alter amanagement function of ID node 120 a.

In another embodiment, the detecting step may comprise having the nodedetect the one or more magnetic field changes in the proximateenvironment to the node when the node has been separated from aplacement support for the node, and where the placement support includesthe source of the magnetic field. This embodiment is exemplified inFIGS. 49A-49B, where placement support 4900 includes magnetic fieldsource 4905 and ID node 120 a is separated from that support 4900 asshown in FIG. 49B.

At step 5110, method 5100 continues with the node altering a managementfunction of the node in response to detecting the magnetic fieldchanges. For an ID node deployed in a wireless node network and being incommunication with a higher level master node, which is in furthercommunication with a server, the ability to be magnetically actuated togenerally alter an operational or management function of the ID node isadvantageous. Various embodiments may alter a node's operation basedupon the change in magnetic fields in a variety of ways.

In one example, the altering step may be accomplished when the nodechanges a power condition of the node in response to the detected one ormore magnetic field changes. In more detail, the node may change thepower condition of the node by selectively energizing the node from apower source (e.g., a battery 355) by actuating a magnetic switchintegrated into the node (such as switch 365 in ID node 120 a shown inFIG. 3) to enable powered operation of the node in response to thedetected one or more magnetic field changes. In that detailed example,the magnetic switch may be wired within the node to separately be ableto cut on and off a power signal that energized all or at least part ofthe ID node. As such, the change in magnetic field operates as a controlmechanism by which the ID node may be turned on from an off position (ormore generally made to change a power state within the ID node—e.g.,from a low power state to an alert or higher power state).

In another example, the altered management function may be having thenode override a power setting previously established in response to aserver command. For example, the node may have recently received acommand from a server (via a message from a master node), and the noderesponded to the command by changing a power setting on the node. Forinstance, the node may have set its RF output power level to a minimumpower level. However, in response to the detected change in magneticfield, the node may override that power setting as a type of alteredmanagement function of the node.

In another example, the altered management function may comprisetransmitting an alert, such as a security alert or movement alert. Morespecifically, the altered management function may comprise having thenode transmit certain relevant information to the master node as a wayor reporting what was detected. The relevant information may, forexample, include a movement alert along with location informationrelated to the node. The movement alert related to the node may updatethe master node that the node has been moved, which may be of concern ifthe expectation is that the node should not be moving. This may causethe master node to also forward such information on to the serverdepending on the content of the movement alerts (e.g., a particularlevel of the alert indicating a quantified extent of urgency andimmediacy for continued hierarchical reporting up to the server). Thelocation information related to the node may help inform the master nodeof any existing or new location or movement direction for the reportingnode.

In another embodiment, the movement alert may indicate a change frombetween moving states—where the node is moving or no longer moving. Inan example, a trailer hitch and related trailer ball may be usedtogether. The ball may be equipped with a magnet (e.g., with support4900 of FIG. 49B implemented as the ball) and the hitch contains a nodewith a magnetic switch (e.g., with ID node 120 a and magnetic switch 365as the node and magnetic switch, respectively). The magnetic switch may,for example, be internal to the node or externally exposed for ease ofphysical pairing and durability. When the magnetic switch connectionbetween the two is changed (e.g., opened), it indicates to the backendserver system (through the uploaded node data), that the trailer nolonger is connected to the towing vehicle. This may be used for yardmanagement of trailers through their location, productivity ofapplications, and security applications where the alert is both amovement alert and a security alert. Those skilled in the art willappreciate that in another embodiment (such as that illustrated in FIGS.50A and 50B), the ball and hitch implementation may be reversed.

In an exemplary security embodiment, the movement alert may be used as asecurity trigger where detected change in magnetic fields may indicatean object may have been illicitly removed. In such a situation, the nodemay immediately start reporting its status. When the message has beencommunicated through a master node to the backend server, the server maydetermine if the break of the connection was expected or the result ofan illicit action

Transmitting the alert may, in another embodiment, be accomplished bytransmitting the alert by the node to a predetermined set of nodes inthe network defined by a filtering mode set by the server. For example,the server may set a “local” or “regional” filtering mode (as explainedwith respect to the Node Filtering Manager part of exemplary servercontrol and management code 525) as a way to manage communicationsbetween nodes and an anticipated communication burden on a master node.The predetermined set of nodes defined by the filtering mode may bethose master nodes which the node is allowed to contact and with whomthe node may associate.

In still another example, the altered management function comprisesaltering association data related to the node. Association data, such asassociation data 340 maintained in memories 320 and 315 on ID node 120a, may reflect a logical connection that is tracked. For example, theassociation may be a passive or active connection of the ID node 120 awith other nodes (such as master node 110 a), and/or an association withone or more objects (e.g., vehicles, buildings, and places).

In a further example, altering association data may involve changing theassociation data to reflect a change in an inventory management aspectof an item related to the node. Use of an exemplary wireless nodenetwork may have nodes associated with items in an inventory (e.g., aninventory of trucks, ULD containers, pallets, etc.). In general, aninventory management aspect of an item related to a node is an aspect ofhow to manage an inventory of such items. In more detail, changing aninventory management aspect may involve changing the association data toindicate movement of the item related to the node, disposal of the itemfrom the inventory, or adding the item to the inventory. For example, atrailer may associated with a magnetically actuated node and thetrailer's node is positioned proximate a magnetic field source that isstationary. When the trailer moves from a storage spot, the movement ofthe trailer and its node away from the stationary magnetic field causesa change in magnetic fields near the node. As a result, the change inmagnetic fields may be detected, and association data may be changed toindicate movement of the trailer. This may also be accompanied by analert, such as a security alert related to movement of the trailer.

In another embodiment, the altered management function comprises loggingusage information for an item related to the node. The detected changein magnetic field may, in some situations, represent movement or use ofthe item related to the node. For example, in the moving trailer examplefrom above, the detected change in magnetic fields may indicate thetrailer is being put into use and the node may log usage information forthe trailer as a resulting type of altered management function. Suchusage information may include, for example, time-related data on whenthe item has been moved relative to a source of the magnetic field. Inother examples, the usage information may also or alternatively includelocation data on where the item is moving, or sensor informationcollected by various environmental sensors on the node to reflect anexposed environment being logged as the item is being used.

In one embodiment, the node may be part of a placement support for amoveable object having a source of the magnetic field. In general, aplacement support may generally be structure that holds, couples to, oris placed next to a moveable object (such as a holster and gunrelationship) where the placement support and the object are typicallyused together. In a more detailed embodiment, the altered managementfunction may comprise logging usage information for the moveable objecthaving the source of the magnetic field. In the embodiment shown inFIGS. 50A-50B, the node 5110 a is stationary while object 5000 ismoveable and the object includes magnetic field source 5010 thatproduces magnetic field 5015. As moved, the object 5000 (shown in FIG.50B) is separated from the placement support 5005 and being used for aparticular purpose. For example, object 5000 may be implemented asequipment (e.g., a handgun, a scanning tool, a piece of mobile testequipment) while placement support 5005 may be implemented as a holderor support for the equipment (e.g., a holster for the handgun, a holsterfor the scanning tool, a charging cradle for the mobile test equipment,etc.). As the object is moved, the magnetic field changes and usageinformation on the object may be collected and logged. Such usageinformation may include information related to time and location data.

In a more detailed example, the stationary node may be incorporated intoor simply be part of a holster. The movable object may be implemented asa scanning gun having a magnet within it so that when the scanning gunis placed in the holster, the magnetic field emanating from the magnetare detected by and exposed to a magnetic switch in the holster's node.When the scanning gun is removed for use scanning codes or labels, themagnetic field is no longer exposed to the node in the holster, and thenode responds to this change in magnetic field by logging usageinformation about the scanning gun.

At step 5115, method 5100 concludes by transmitting, by the node to themaster node, information about the altered management function to beforwarded to the server. For example, an ID node may transmit a messageto an associated master node where the message reports the alteredmanagement function (e.g., logged usage information, an alert aboutmovement of the item, etc.). The message also will have the master nodeforwarding it to the server so that the server may be kept up to date onthe ID node and updates from it, such as whether it is moving, whetherinventory is changing, whether items that are moving are a securityissue, etc.

Additionally, method 5100 may involve a selection of which managementfunction to alter. In other words, the detecting of changing magneticfields may allow for an alternative type of command input for a wirelessnode. For example, a type of code may be used for a particular numberand/or duration of magnetic field changes detected, which maycollectively indicate a certain management function to be altered by thenode. In more detail, the multiple magnetic field changes may include aseries of magnetic field changes over a period of time. These changesmay be a detected pattern of changes. As such, the node's magneticswitch integrated within a magnetically actuated node may be implementedsuch that it may detect (or in combination with the node processingunit) the series of magnetic field changes over the period of time.

In a more detailed embodiment, multiple conditions may be monitored fordetection from the magnetic field changes. For example, when there is adetected change on the magnetic switch, based upon a first stage or afirst condition, the node monitors and attempts to detect a second stageor second condition while also causing a first management function to bechanged. In other words, an embodiment may nest conditions and differentaltered management functions based upon the different conditions (e.g.,setting alerts based upon movement, time or other conditions).

Those skilled in the art will appreciate that method 5100 as disclosedand explained above in various embodiments may be implemented on a node,such as exemplary ID node 120 a as illustrated in FIG. 5 (or ID node 120a illustrated in FIGS. 48A-48C and 49A-49B, or ID node 5110 aillustrated in FIGS. 50A-50B), running one or more parts of a controland management code (such as code 325) to implement any of the abovedescribed functionality. Such code may be stored on a non-transitorycomputer-readable medium (such as memory storage 315 within an exemplaryID node). Thus, when executing such code, a processing unit (such asunit 300 within a ID node) may be operative to perform operations orsteps from the exemplary methods disclosed above, including method 5100and variations of that method.

In yet another embodiment, a magnetically actuated node (such as an IDnode) is described for magnetically altering an operation of the node ina wireless node network. The magnetically actuated node comprises a nodeprocessing unit, and a node memory coupled to the node processing unit.The node memory maintains code for execution by the node processingunit, such as code 325. The magnetically actuated node further comprisesa first communication interface coupled to the node processing unit andis operative to communicate directly over a first communication pathwith a master node. The master node is deployed in communication with aserver in the network over a second communication path.

The node further includes a magnetic switch having an output coupled tothe node processing unit. The control of the magnetic switch isresponsive to one or more magnetic field changes in a proximateenvironment of the magnetically actuated node.

The node also includes a power source for selectively energizing themagnetically actuated node. In one embodiment, the power source is abattery that provides electrical power to the components of the node. Inone embodiment, the exemplary power source may be coupled to themagnetic switch such that the magnetic switch operates as a switchbetween the power source and the rest of the components of the node (orat least a subset of the components of the node).

The processing unit of the node, when executing the code maintained onthe memory, is operative to perform particular steps and operationssimilar to those explained above with respect to the various embodimentsof method 5100. In particular, the processing unit is operative to altera management function of the magnetically actuated node when themagnetically actuated switch responds to the one or more magnetic fieldchanges and sends a response signal from the output of the magneticallyactuated switch to the node processing unit, and transmit a message tothe master node, the message comprising information about the alteredmanagement function to be forwarded to the server.

In a related embodiment, the magnetically actuated node may furtherinclude a second communication interface and location circuitry. Thesecond communication interface may be coupled to the node processingunit and operative to communicate over the second communication pathwith the server. The location circuitry has an input coupled to anantenna that receives location signals, such as GPS signals. Thelocation circuitry also may have an output coupled to the nodeprocessing unit such that the circuitry receives one or more locationsignals in the input from the antenna and provide a determined locationof the magnetically actuated node on the output to the node processingunit.

In another embodiment where the shipping ID node may be further utilizedas an alarm sensor, the node may be configured or attached relative to adoor along with a magnet on the door jamb (or vice versa). Upon openingof the door, the magnet and the node (having the magnetic switch) areseparated causing a detection of a magnetic field change. As such, thenode may transmit an alarm message to another node (or user accessdevice operating as a node) or to the server for further distribution ofthe alarm message. Thus, an embodiment of the ID node may be used afterthe package is delivered as a type of mobile intrusion detection system.

Furthermore, those skilled in the art will recognize that exemplarynetwork components shown in FIGS. 48A-50B depict an exemplaryinteractive system that uses an exemplary magnetically actuated node.Such an exemplary system includes server 100 as well as magneticallyactuated node (such as ID node 120 a having magnetic switch 365, or node5110 a having a magnetic switch embedded within it), master node 110 a,and server 100 as described above in more detail. Additionally, theexemplary system embodiment shown in FIGS. 48A-50B may have themagnetically actuated node operate as described with respect to method5100 and variations of that method as explained in more detail above.

Integrated Node in Communications Coupler or Adaptor

In one embodiment, a network device, such as an ID node or master node,may also be useful in a remote monitoring situation and especially whenmonitoring signals exchanged between conveyances (e.g., between atractor and its trailer, between two trailers, between different railwayvehicles, between a towing maritime vehicle and a towed barge, etc.). Bymonitoring such signals using a node, the wireless node network may beused to detect when there are problems (e.g., the trailer isdisconnected from its tractor) and report a status without having tointerfere with the electronic systems communicating onboard therespective conveyances. As such, an embodiment may monitor withouthaving to interfere or make changes to any detected data orcommunications between such conveyances.

Conventionally, tractors and trailers (like many other types of knownconveyances or means for transportation) may be mechanically coupledtogether so that the tractor can pull the trailer with its cargo in anefficient and cost effective manner. Various links between the tractorand the trailer may provide vehicle subsystems with power or othersignals to operate, e.g., lights, brakes. Thus, hydraulic, pneumatic,electrical, and other subsystems on the tractor/trailer combination mayhave associated electrical conductors and pneumatic lines running therebetween so these subsystems can operate appropriately and in acoordinated fashion onboard the two conveyances.

In some situations, the electrical subsystems of both the tractor andtrailer operate in a manner which requires coordination between theelectrical components on each to operate the tractor/trailer combinationsafely and effectively. Conventionally, in order to coordinate suchoperation and to supply power from the tractor to the trailer, aseven-pin connector has been used by the trucking industry to accomplishthese and other electrical objectives. The connector includes two matedand coupler connectors that can be disengaged or engaged to permit thetractor and trailer combination to be connected in order to communicateand disconnected when the tractor and trailer need to separate. Theseseven-pin connectors also are well known and have been specified by theSociety of Automotive Engineering “SAE” according to the standard numberJ560 (hereinafter referred to as “SAE J560”).

FIG. 54 is a diagram illustrating an exemplary coupler connectionbetween two conveyance systems having an integrated node in accordancewith an embodiment of the invention. Referring now to FIG. 54, a vehicle5405 (such as a tractor or truck) and its trailer 5400 are illustratedin a simplistic manner as being connected together. Specifically, anelectronic system aboard vehicle 5405 (such an anti-lock braking system(ABS) for the vehicle) communicates with an electronic system aboardtrailer 5400 (such as the ABS system for the trailer) over a couplerconnection that provides a communication path (e.g., multiple power andsignal lines) for signals passing between the vehicle 5405 and trailer5400. In more detail, as shown in the example illustrate in FIG. 54, anexemplary coupler connection may include a set of mated couplerconnectors—e.g., male coupler connector 5410 and female couplerconnector 5420. Male coupler connector 5410 is shown having pins 5415extending from a face of the connector and a cable 5425 on the back ofthe connector. Those skilled in the art will appreciate that cable 5425is operatively connected to an electronic system, such as an ABS system,onboard trailer 5400. The pins 5415 from the male coupler connector 5410mate with sockets (not shown in detail) in female coupler connector5420, which has a similar cable 5430 to a similar electronic systemonboard vehicle 5405.

In one embodiment, a node (generally referred to as a network device)may be deployed and disposed within the coupler connection. As shown inFIG. 54, an ID node 5411 is shown integrated as part of the male couplerconnector 5410 and connectable to master node 110 b, which maycommunicate with server 100 in an exemplary wireless node network. Ingeneral, node 5411 can be powered (or charged) through a power linepassing through the coupler connection. The node 5411 may essentiallymonitor, detect, and record data that appears on the signal linespassing through the coupler connection, and provide such data wirelesslyvia broadcasts from the node. As such, node 5411 is able to detect whentrailer 5400 is disconnected from vehicle 5405 as well as monitor theoperating conditions of the vehicle 5405 and trailer 5400 to the extentsuch conditions are apparent from any of the signals passing through thecoupler connection.

FIG. 55 is a more detailed diagram illustrating the exemplary couplerconnector between two systems having an integrated node in accordancewith an embodiment of the invention. Referring now to FIG. 55, malecoupler connector 5410 is shown in more detail with ID node 5411, pins5415, and cable 5425. More specifically, male coupler connector 5410 isshown with ID node 5411 integrated as part of the coupler and, moregenerally, disposed within the coupler. In another embodiment, a similarID node may be integrated within a female coupler instead of the malecoupler.

As shown in FIG. 55, pins 5415 are essentially ends of signal lines thatpass through the coupler connector 5410 and extend out of the face ofcoupler connector 5410. In this example, one of the signal lines is apower line that may provide power from vehicle 5405 to trailer 5400. Assuch, ID node 5411 may take advantage of the power line, which may beconnected with a power connection 5414 to ID node 5411. Those skilled inthe art will appreciate that power connection 5414 may include both aground and a supply voltage in order to energize and power circuitrywithin ID node 5411.

And as shown in FIG. 55, ID node 5411 also includes signal monitorcircuitry 5412 that has a collective input (e.g., the separateconnections 5413 to different signal lines in the coupler connector5410) and an output (not shown) coupled to the processor of the ID node5411. In general, the output provides detected data from the signallines being monitored on inputs 5413 to the processing unit. In moredetail, the signal monitor circuitry 5412 may be implemented usingperipheral circuitry described for an ID node with respect to FIG. 3(e.g., various peripherals such as timer circuitry, USB, USART,general-purpose I/O pins, IR interface circuitry, DMA circuitry,additional logic chips, and relays that make up the ID node).

While FIGS. 54 and 55 illustrate an exemplary integrated ID nodedisposed within a coupler connection as part of one of the mated couplerconnectors, other embodiments may not require a special integrated nodecoupler connector dedicated to a particular conveyance, such as avehicle 5405 or trailer 5400. In particular, an embodiment may deploy anode (more generally a network device) as part of an adapter that can bepart of a coupler connection. With such a node-enabled adapter beingplaced in-line with an existing convention mated coupler connector pair,a greater applicability may be achieved as the adapter may be used inless dedicated situations.

FIG. 56 is a diagram illustrating another exemplary coupler connectionbetween two conveyance systems having an adapter node in accordance withan embodiment of the invention. As shown in FIG. 56, an exemplaryadapter 5610 is disposed between a mated set of coupling connectors(male coupler connector 5605 and female coupler connector 5420). Theadapter 5610 is essentially a plug adapter between the connectors andincludes an ID node 5611 integrated within the adapter 5610 in much thesame way as ID node 5411 is shown integrated within connector 5410 inmore detail in FIG. 55.

While FIGS. 54-56 are illustrated showing exemplary conveyances as avehicle 5405 and a trailer 5400, other types of conveyances or modes oftransportation may also be applicable. In more detail, such exemplaryconveyances may include, but are not limited to, different types ofvehicles (e.g., an automobile, a truck, a tractor, farm equipment,construction equipment, marine vehicles, a locomotive, etc.) andtrailers (as well as barges, trams, buses, other railway vehicles,etc.).

Additionally, those skilled in the art will appreciate that suchintegrated nodes as ID node 5611 and 5411 may be deployed innon-conveyance examples in other embodiments between disparately locatedelectronic modules that need to communicate over a connecterizedcommunication path. For example, a generator may be temporarily deployedto provide power and a node may be integrated into an adapter orconnector as part of a coupler connection between the generator and whatmay be powered by the generator. Thus, the node may provide informationrelated to the status of the generator without interfering with theoperation of the generator.

FIG. 57 is a flow diagram illustrating an exemplary method formonitoring at least one signal passing through a coupling connectionhaving a network device that communicates on a wireless node network inaccordance with an embodiment of the invention. Referring now to FIG.57, method 5700 begins at step 5705 with the network device monitoringat least one signal line passing through the coupling connection from afirst conveyance to a second conveyance (e.g., one or more of the linesmonitored by connections 5413 of signal monitoring circuit 5412 in IDnode 5411 shown in FIG. 55).

As mentioned, a network device is a general designation for a component,in the wireless node network in embodiments. In one embodiment, thenetwork device may be an ID node operative to communicate directly witha master node in the wireless network but not operative to communicatedirectly with a server (another entity in the wireless node network). Inanother embodiment, the network device is a master node operative tocommunicate directly with a server as another entity in the wirelessnode network.

The coupling connection, for example, may comprise a mated set ofconnectors such that the network device may be integrated into one ofthe mated connectors. In the example shown in FIG. 55, ID node 5411 (atype of network device) is illustrated as being integrated into the malecoupling connector 5410. However, those skilled in the art willappreciate that such a network device may also be integrated into thefemale coupling connector 5420.

In one embodiment, the coupling connection comprises an adapter disposedbetween a mated set of coupling connectors and, as such, the networkdevice is integrated as part of the adapter. For example, FIG. 56illustrates an exemplary adapter 5610 having ID node 5611 (a type ofnetwork device) integrated as part of adapter 5610. In anotherembodiment, the adapter may be disposed between a mated set of anti-lockbraking system connectors linking a vehicle to a trailer.

Referring back to step 5705, method 5700 monitors at least one signalline passing through the coupling connection from the first conveyanceto the second conveyance. In one embodiment, the first conveyance is avehicle and the second conveyance is a trailer. A vehicle, in thisembodiment, is a general term for a transport, and may include (as notedabove) an automobile, a truck, a bus, a tractor, farm equipment,construction equipment, marine vehicles, a locomotive (a type of railwayvehicle). Likewise, an exemplary trailer is a general term for transportequipment that is towed or pushed, such as a barge, carriage cars ontrams, railway cars (another type of railway vehicle) towed or pushed bya locomotive. Other examples of conveyances may include a maritimeconveyance (e.g., marine vessel, tugboat, ship, boat) where a secondconveyance may be implemented as a maritime barge that is coupled to thetowing maritime vessel and having a coupling connection between variouselectronic systems on the respective conveyances.

At step 5710, the network device detects data on the monitored signalline. For example, as shown in FIG. 55, data on one or more of thesignal lines going through cable 5425 and connector 5410 may be detectedusing connections 5413 of signal monitoring circuitry 5412 on ID node5411. For example, the data may include useful electronic informationflowing from one conveyance to another (and vice versa) indicating astatus of operations between and/or of the respective conveyances. Inanother example, such monitoring may detect when the first conveyanceand the second conveyance are disconnected based upon the monitoredstatus of the at least one signal line.

In a more general embodiment, the detecting step may further have thenetwork device detecting a change in state for the coupling connection.For example, the change in state for the coupling connection may reflecta change in power flowing from the first conveyance to the secondconveyance. When one of the conveyances begins drawing more powerthrough the coupling connection, this change in the coupling connectionsstate may be recorded and reported to another node or server in thewireless node network.

In a further example, the change in state for the coupling connectionmay reflect a changed RF environment detected by the network device.Thus, detecting more RF signals above a threshold amount or a change inRF power levels over a threshold level may reflect a change in state forthe coupling connection and the related first and second conveyances towarrant reporting such a change. In more detail, one of the conveyancesmay have a characteristic RF signature, which may be reported with sucha change in state.

At step 5715, the network device records the detected data. For example,ID node 5411 shown in FIG. 55 may record data detected on the threesignal lines monitored in volatile memory 320 and memory storage 315 foran exemplary ID node. In another example, sensors 360 may implementsignal monitoring circuitry 5412 and include onboard monitoring memoryto temporarily record the data being monitored. The processing unitwithin ID node 5411 may, at some point, move the data from memory withinthe sensor 360 to a larger capacity memory storage 315 for longer-termstorage before sharing or uploading the data to other network entities,such as master node 110 a and server 100.

At step 5720, the network device transmits the detected data to anotherentity in the wireless network. For example, ID node 5411 shown in FIG.55 may access the recorded data and transmit that data as the detecteddata over a communication interface to master node 110 a, which mayforward the data to server 100. In an embodiment where the networkdevice is a master node, that master node may transmit the detected datato another master node or directly to the server.

In one embodiment, transmission of the detected data to another entityin the network may comprise providing a message to a server in thewireless network (directly if the network device is a master node, orindirectly if the network device is an ID node). The message may includethe recorded data and a notification of a status related to the firstconveyance and the second conveyance, such as that they aredisconnected.

In still another embodiment, method 5700 may have the network devicereceiving power from a power line passing through the couplingconnection. For example, as shown in FIG. 55, ID node 5411 receivespower from a power line passing through the male coupler connector 5410via a power connection 5414.

Those skilled in the art will appreciate that method 5700 as disclosedand explained above in various embodiments may be implemented on networkdevice, such as an ID node (e.g., exemplary ID node 120 a as illustratedin FIG. 3, ID node 4511 as illustrated in FIGS. 54 and 55, or ID node5611 as illustrated in FIG. 56) or a master node (e.g., exemplary masternode 110 a as illustrated in FIGS. 4, and 54-56), running one or moreparts of a control and management code (such as code 325 when thenetwork device is implemented as an ID node or code 425 when the networkdevice is implemented as a master node) to implement any of the abovedescribed functionality. Such code may be stored on a non-transitorycomputer-readable medium (such as memory storage 315 within an exemplaryID node or memory storage 415 within an exemplary master node). Thus,when executing such code, a processing unit of the network device (suchas unit 300 within an ID node or unit 400 within a master node) may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 5700 and variations of that method.

In yet another embodiment, an apparatus is described for monitoring atleast one signal passing from a first conveyance to a second conveyance.The apparatus comprises a coupling connection and a network devicedisposed within the coupling connection. The coupling connectionprovides a communication path for one or more signals passing betweenthe first conveyance and the second conveyance, such as ABS signalspassing through a connection between a tractor and a trailer.

The network device is in connection with signals passing through thecoupling connection, and further comprises a processing unit, a memory,a communication interface, and a signal monitor circuit. The memory iscoupled to the processing unit and maintains code for execution by theprocessing unit. The memory, at times, may also maintain detected andrecorded data as explained in more detail below. The communicationinterface is coupled to the processing unit and operative to communicatewith another network device (such as an ID node, a master node, or aserver) in a wireless node network.

In one embodiment where the network device is an ID node, thecommunication interface may be a short-range communication interfacesuch that the processing unit of the network device is operative tocommunicate directly with a master node as the another network device inthe wireless node network over the short-range communication interfacebut unable to communicate directly with a server in the wireless nodenetwork.

In another embodiment where the network device is a master node, thenetwork device may also include a longer-range communication interfacecoupled to the processing unit. This longer-range communicationinterface may be operative to communicate with a server in the wirelessnode network.

The signal monitor circuit of the network device has an input andoutput. The input is coupled to the one or more signal lines passingthrough the coupling connection on the communication path between thefirst conveyance and the second conveyance. The output provides detecteddata from the at least one signal line to the processing unit.

The processing unit of the network device, when executing the codemaintained on the memory, is operative to perform particular steps andoperations similar to those explained above with respect to the variousembodiments of method 5700. In particular, the processing unit isoperative to monitor the detected data provided from the signal monitorcircuit, record the detected data to the memory for sharing with theanother network device in the wireless node network, and transmit therecorded data over the communication interface to the another networkdevice in the wireless network. The processing unit, in various furtherembodiments, may also be operative to perform steps as described in moredetails above with respect to the embodiments of method 5700.

Distributed Operation Applications

Sharing Shipment Condition Information Between Nodes

Rather than require network devices, such as ID nodes or master nodes,to always obtain certain types of data (e.g., environmental data,location data) from the backend server, an embodiment may allow anetwork device to share data with another network device in certainsituations for more efficient network operations. In other words, anembodiment may distribute the operation of sharing certain types of datafrom the server to allow more efficient node-to-node sharing of thedata.

In general, certain information may be shared between nodes (types ofnetwork devices) when, for example, the nodes and their respectivepackages are traveling together. For example, context data may indicatenodes and their respective packages are traveling together (e.g.,context data may indicate certain nodes are part of a group of packagesconfined on a pallet or within a ULD). In such a situation, a node mayneed to know information about additional context data generallyreferred to as shipment condition information (such as locationinformation, ambient or anticipated environmental information, updatedsystem information, and the like related to shipping of the packages).This shipment condition information may be obtained by a node seekingsuch information from a node already possessing such information if itis authorized.

Generally, exemplary shipment condition information may exist or begenerated or obtained in various ways. For example, shipment conditioninformation may be generated from sensor data (e.g., environment,temperature, light, pressure, humidity). In another example, shipmentcondition information may be provided to a node by the server onrequest. In still another example, the shipment condition informationmay be pre-staged by the server on the node so that the node need notsend the server a request for such information in the first place.

Additionally, exemplary shipment condition information may takedifferent forms. For example, the shipment condition information mayinclude environmental information, location information, updated systeminformation needed for consistent and coordinated node operations, andthe like.

In various embodiments, nodes may be authorized to share such shipmentcondition information by various means. For example, a node may beauthorized to share such information with another node by requestingauthority to do so from the server or having requested such authoritybefore so as to be pre-authorized for the current sharing opportunity.In another example, a node may be pre-authorized to share only certaintypes of shipment condition information (e.g., a first node isauthorized to share only temperature information with a second node, butnot other types of shipment condition information).

FIG. 58 is a flow diagram illustrating an exemplary method for sharingshipment condition information in a wireless node network having aplurality of network devices and a server in accordance with anembodiment of the invention. Referring now to FIG. 58, method 5800begins at step 5805 where a first node (one of the network devices)detects an advertising signal broadcast from a second node (another ofthe network devices). The first node is related to a first package,while the second node is related to a second package. For example, thefirst node may be related to one package in a palletized shipment ofpackages where the second node may be related to another package in thepalletized shipment. These two nodes are being shipped and will traveltogether during at least part of the shipping transit journey.

In one embodiment, the first node may receive the shipment conditioninformation from another of the network devices (e.g., an ID node, amaster node, or the server) in the network before storing the shipmentcondition information on the memory in the first node.

In another embodiment, the first node may receive the shipment conditioninformation from a sensor before storing the shipment conditioninformation on the memory in the first node. For example, as shown inFIG. 3, ID node 120 a includes sensors 360, which may gatherenvironmental information (such as information on light, temperature,humidity, pressure, altitude, magnetic field strength, acceleration,vibration, impact, and orientation) about a proximate environment to thefirst node, such as an environment physically proximate and/or proximatein time. In other words, the shipment condition information may beenvironmental information about a physically proximate environment tothe first node in one embodiment (such as the temperature outside anode, which may be used along with context data on packaging materialsto estimate shipment condition temperature within the package).

In another embodiment, the shipment condition information may beenvironmental information about an environment anticipated to beproximate the first node at some time in the future. In more detail, IDnode 120 s may gather humidity information about the area and regionsurrounding the ID node 120 a and store that information as shipmentcondition information in memory storage 315 as part of shared data 345.In another embodiment, the shipment condition information may compriselocation information about the first node or updated system information(such as a common time setting dictated by the server so that allnetwork devices are coordinated).

At step 5810, method 5800 associates the first node and the second node.Associating the first and second node may establish an authorizedconnection between the two nodes that may allow for secure sharing ofinformation. Such an association may also be recorded as associationdata on the nodes.

At step 5815, method 5800 continues where the first node accesses theshipment condition information from the memory in the first node. Forexample, ID node 120 a may access memory storage 315 to access exemplaryshipment condition information maintained as shared data 345. Thoseskilled in the art will appreciate that if the first node is implementedas a master node in an embodiment, exemplary master node 110 a (asillustrated in FIG. 4) may likewise access memory storage 415 to accessexemplary shipment condition information maintained as shared data 445.

In more detail, the first node may access the shipment conditioninformation as pre-staged information stored in the memory in the firstnode.

At step 5820, method 5800 concludes with the first node transmitting theshipment condition information to the second node if the first node isauthorized to share the shipment condition information with the secondnode. In one embodiment, the first node may transmit the shipmentcondition information to the second node if the first node waspre-authorized to share the shipment condition information with thesecond node. In another embodiment, the first node may transmit theshipment condition information to the second node if the first node waspre-authorized to share a designated type of shipment conditioninformation with the second node and the shipment condition informationaccessed is the designated type of shipment condition information.

In another embodiment, method 5800 may also have the first node settinga status flag to indicate the first node has shipment conditioninformation to be shared. In a more detailed example, the status flagmay be information in an advertising signal broadcast by the first node(e.g., in a header of an advertising packet message broadcast by thefirst node after obtaining the shipment condition information to beshared).

In still another embodiment, method 5800 may also include the first nodereceiving a request from the second node in response to the advertisingsignal broadcast by the first node, where the request asks for the firstnode to directly share the shipment condition information with thesecond node without requesting the shipment condition information fromthe server. Thus, an embodiment using information from the advertisingsignal (e.g., the status flag) may indicate that the first node hasshipment condition information available to be shared via the signalinformation such that when the second node receives the signal, thesecond node may request the information, log and update relevant updatedsettings with the shared shipment condition information (e.g., a newclock reading, a new temp reading) without having to upload from thebackend server.

Those skilled in the art will appreciate that method 5800 as disclosedand explained above in various embodiments may be implemented on anetwork device, such as an ID node (e.g., exemplary ID node 120 a asillustrated in FIG. 3) or a master node (e.g., exemplary master node 110a as illustrated in FIG. 4), running one or more parts of a control andmanagement code (such as code 325 when the network device is implementedas an ID node or code 425 when the network device is implemented as amaster node) to implement any of the above described functionality. Suchcode may be stored on a non-transitory computer-readable medium (such asmemory storage 315 within an exemplary ID node or memory storage 415within an exemplary master node). Thus, when executing such code, aprocessing unit of the network device (such as unit 300 within an IDnode or unit 400 within a master node) may be operative to performoperations or steps from the exemplary methods disclosed above,including method 5800 and variations of that method.

While FIG. 58 explained an embodiment for sharing shipment conditioninformation from the perspective of the network device (e.g., ID node ormaster node) having the information and sharing it with another node,FIG. 59 explains a similar embodiment for requesting shared shipmentcondition information from the perspective of the network devicereceiving that shared information. In other words, FIG. 59 is a flowdiagram illustrating an embodiment with an exemplary method forrequesting shared shipment condition information after one of thenetwork devices senses another of the network devices has suchinformation. Referring now to FIG. 59, method 5900 begins at step 5905where a second node detects an advertising signal broadcast from a firstnode. The first node is one of the network devices and is related to afirst package, while the second node is another of the network devicesand is related to a second package.

At step 5910, the second node determines that the first node hasshipment condition information to share based upon status information inthe advertising signal broadcast from the first node. In one embodiment,the shipment condition information may have been generated by the firstnode (such as sensor data generated by a first node having sensors). Inanother embodiment, the shipment condition information may have beengenerated by the server and provided to the first node. In yet anotherembodiment, the shipment condition information may comprise pre-stageddata stored on a memory of the first node.

In an embodiment, the shipment condition information may includeenvironmental information about a proximate environment to the firstnode (such as at least one of light, temperature, humidity, pressure,altitude, magnetic field strength, acceleration, vibration, impact, andorientation). In other embodiments, this proximate environment may be aphysically proximate environment to the first node or an environmentanticipated to be proximate the first node at another time. In stillanother embodiment, the shipment condition information may compriselocation information about the first node.

In yet another embodiment, the shipment condition information maycomprise updated system information, such as a new clock reading for thenode to use so that operations may be better coordinated and moresynchronized.

At step 5915, method 5900 associates the first node and the second node.As explained with respect to step 5810 in FIG. 58, associating the firstand second node may establish an authorized connection between the twonodes that may allow for secure sharing of information. Such anassociation may also be recorded as association data on the nodes.

At step 5920, the second node transmits a request for the shipmentcondition information if the status information indicates the first nodehas the shipment condition information to share. Thus, the second nodeis informed of the availability of sharable data via the statusinformation and, if such data is desired, transmits the request.

At step 5925, method 5900 concludes when the second node receives theshipment condition information from the first node if the first node isauthorized to share the shipment condition information with the secondnode. In one embodiment, the second node receives the shipment conditioninformation from the first node if the first node was pre-authorized toshare the shipment condition information with the second node. Inanother embodiment, the second node receives the shipment conditioninformation from the first node if the first node was pre-authorized toshare a designated type of shipment condition information with thesecond node and the shipment condition information requested is thedesignated type of shipment condition information

Those skilled in the art will appreciate that method 5900 as disclosedand explained above in various embodiments may be implemented on anetwork device, such as an ID node (e.g., exemplary ID node 120 a asillustrated in FIG. 3) or a master node (e.g., exemplary master node 110a as illustrated in FIG. 4), running one or more parts of a control andmanagement code (such as code 325 when the network device is implementedas an ID node or code 425 when the network device is implemented as amaster node) to implement any of the above described functionality. Suchcode may be stored on a non-transitory computer-readable medium (such asmemory storage 315 within an exemplary ID node or memory storage 415within an exemplary master node). Thus, when executing such code, aprocessing unit of the network device (such as unit 300 within an IDnode or unit 400 within a master node) may be operative to performoperations or steps from the exemplary methods disclosed above,including method 5900 and variations of that method.

In another embodiment, a system is disclosed for sharing shipmentcondition information in a wireless node network. The system generallycomprises a first node in the network and a second node in the network.The first node in the system is related to a first package being shippedand generally comprises a first processing unit, a first memory, and afirst communication interface. The first processing unit is coupled toeach of the first memory and the first communication interface. Thefirst memory maintains a first code (e.g., code 325 or code 425depending on whether the node is an ID node or master node) forexecution by the first processing unit. The first memory also maintainsthe shipment condition information.

In a further embodiment, the first node may also be implemented as asensor node (another type of network device similar to an ID node asdiscussed above in more detail) and include a sensor coupled to thefirst processing unit. The sensor may generate sensor data as theshipment condition information maintained in the first memory.

The second node in the system is related to a second package beingshipped and generally comprises a second processing unit, a secondmemory, and a second communication interface. The second processing unitis coupled to each of the second memory and the second communicationinterface. The second memory maintains a second code (e.g., code 325 orcode 425 depending on whether the node is an ID node or master node) forexecution by the second processing unit.

During operation of the system, the first node and the second node areoperative under the control of their respective codes, to interact andshare the shipment condition information under certain conditions. Inparticular, the first processing unit of the first node, when executingthe first code maintained on the first memory, is operative to accessthe shipment condition information on the first memory and broadcast anadvertising signal over the first communication interface. Theadvertising signal broadcast has status information on whether the firstnode has the shipment condition information to share. The firstprocessing unit is also operative to receive a request from the secondnode over the first communication interface. The request asks the firstnode for the shipment condition information. The first processing unitis further operative to associate the first node and the second node,and transmit the shipment condition information to the second node overthe first communication interface if the first node is authorized toshare the shipment condition information with the second node.

In one embodiment, the first processing unit of the first node may alsobe operative to receive the shipment condition information from a serverin the wireless node network. In another embodiment, the shipmentcondition information maintained on the first memory may comprise atleast one of pre-staged data, environmental information (such as light,temperature, humidity, pressure, altitude, magnetic field strength,acceleration, vibration, impact, and orientation) about a proximateenvironment to the first node (such as a physically proximateenvironment or an environment proximate in time with respect to thenode), location information about the first node, and/or updated systeminformation (such as a time setting).

Additionally, the second processing unit of the second node, whenexecuting the second code maintained on the second memory, is operativeto detect the advertising signal broadcast from the first node anddetermine that the first node has the shipment condition information toshare based upon the status information in the advertising signalbroadcast from the first node. The second processing unit in the systemis then operative to transmit the request for the shipment conditioninformation to the first node over the second communication interface ifthe status information indicates the first node has the shipmentcondition information to share, and receive the shipment conditioninformation from the first node when the first node is authorized toshare the shipment condition information with the second node.

In a further embodiment of the system, the first processing unit may befurther operative to receive an authorization from the server in thewireless node network, where the authorization permits the first node toshare the shipment condition information with the second node. Inanother example of the system, the first processing unit may be furtheroperative to transmit the shipment condition information to the secondunit over the first communication interface if the first node waspre-authorized to share the shipment condition information with thesecond node. In still another example of the system, the firstprocessing unit may be further operative to transmit the shipmentcondition information to the second unit over the first communicationinterface if the first node was pre-authorized to share a designatedtype of shipment condition information with the second node and theshipment condition information accessed in the first memory is thedesignated type of shipment condition information.

Hierarchical Sensor Network for Multi-Piece Shipments

As mentioned above, certain types of shipments may include a set ofpackaged items. In some situations, such related packages may be groupedtogether and shipped as together (such as on a shipping pallet or withina shipping container). Those skilled in the art will appreciate thatrelated packages being shipped together may be referred to as amulti-piece shipment that may share the same origin and destination (orat least share a portion of a predicted shipping route where thepackages are intended to be shipped together). In an embodiment, anetwork of hierarchically configured nodes may be used to provideinformation about the shipment, more specifically, different parts ofthe shipment, as the multi-piece shipment is being shipped.

In general, a master node is higher in the hierarchy than an ID node. Amaster node is generally more complex and more expensive than an IDnode, which advantageously allows a distribution of sensing functions tothe lower complexity, lower cost ID nodes. In one embodiment, the highercomplexity master node is able to communicate directly with a serverover a first (e.g., longer range) communication path, while being ableto communicate with the lower level and complexity ID nodes over asecond (e.g., shorter range) communication path different from thefirst.

FIG. 60A is a diagram illustrating an exemplary group of nodesassociated with a multi-piece shipment of packages in an exemplaryshipping container in accordance with an embodiment of the invention.Referring now to FIG. 60A, shipping container 6000 is shown havingpackages 6005, 6010, 6015, and 6020 within container 6000. Within eachof the packages is a network device—in particular, a mobile master node6110 a is placed within package 6005, ID node 6120 a is placed withinpackage 6010, ID node 6120 b is placed within package 6015, and ID node6120 c is placed within package 6020. Mobile master node 6110 a cancommunicate with server 100 via the network 105, but can alsocommunicate with each of the ID nodes 6120 a-6120 c via a short rangecommunication path (e.g., a Bluetooth® enabled communication path shownwith dashed lines in FIGS. 60A and 60B).

A shipping customer may selectively identify a group of packages withinthe set of packages in the container or on the pallet. Thus, anembodiment may allow the shipping customer to identify a group or“cloud” of nodes based on the packages selected so that the shippingcustomer may monitor those packages and the shipment conditions withinand around them. Additionally, an embodiment may allow the shippingcustomer to be proactively notified when the personalized cloud of nodesdetects when a package is leaving the group. For example, if an ID nodereports shipment condition information for a particular package thatincludes location information for that ID node, and that locationinformation diverges from the location information gathered from otherID nodes in other packages in the group, the mobile master node maynotify the server, which may access shipping information on the groupand proactively contact the shipping customer in a designated manner(e.g., via an email message, a phone call, a text message, or the like).

In one embodiment, when initially preparing the set of packages6005-6020 for shipment as a group, the nodes may be placed and enabledwithin their respective packages to function as a hierarchical sensornetwork of nodes as one or more of the ID nodes sense shipment conditioninformation relevant to particular packages in the group while beingmanaged by mobile master node 6110 a. For example, such a network may beimplemented as a personal cloud of nodes that may sense shippingcondition information on some or all of the packages in the group.

While the embodiment illustrated in FIG. 60A has the packages beingplaced and confined into a shipping container 6000 (such as a ULD) as agroup, another embodiment may place the node-enabled packages on thesame shipping pallet 6025 as shown in FIG. 60B. In one embodiment, ashipping pallet is a type of flat transport structure that supportspackaged and unpackaged items in a stable fashion so as to be movedabout as a unit. Exemplary shipping pallets may confine the packages viastrapping, stretch wrap, or other covering material that helps to holdthe packages in place on the pallet.

Those skilled in the art will appreciate that embodiments may have agrouped set of packages where not all of the packages are node-enabled.For example, nodes may be placed and enabled within only packages havingselect exterior facing positions with the group of packages. This mayhelp to cost effectively monitor for humidity and light detected as aresult of damage to the exterior ones of the packages as they arearranged in the container or pallet. In another example, including nodesin only a portion of the packages may help effectively monitor fortemperature at designated parts of the configured group of packages andavoid the expense and operational overhead incumbent when all packagesin the group are node-enabled.

In an embodiment, the ability to require the only one of the nodesplaced in the packages of the group be a mobile master node of highercomplexity and cost, allows for an overall lower cost implementation fora sensor network to monitor a group of packages.

FIG. 61 is a flow diagram illustrating an exemplary method of serveroperations when creating a hierarchical sensor network for a grouped setof packages being shipped in accordance with an embodiment of theinvention. Referring now to FIG. 61, method 6100 begins at step 6105with the server associating the mobile master node with one of thepackages in the grouped set of packages. In one embodiment, theassociating is commonly direct (e.g., with nodes in direct contact witheach other as part of the association process) but may be indirect inother embodiments (e.g., using scanned machine readable or humanreadable association information). Such associating may take the form ofrecording association data to reflect the association between the mobilemaster node and the package. The mobile master node is operative tocommunicate directly with the server in the wireless node network over afirst communication path, such as a longer range communication path.

In one embodiment, the grouped set of packages may comprise a palletizedgroup of packages being shipped together. For example, as shown in FIG.60B, packages 6005-6020 are a palletized group of packages secured toshipping pallet 6025. However, in another embodiment, the grouped set ofpackages may comprise a group of packages together within a shippingcontainer, such as container 6000 shown in FIG. 60A.

At step 6110, method 6100 continues with the server associating the IDnode with another of the packages in the grouped set of packages, wherethe ID node is operative to communicate directly with the mobile masternode over a second communication path but not operative to communicatedirectly with the server over the first communication path. Suchassociating of the ID node may take the form of recording associationdata to reflect the association between the ID node and the relevantpackage.

At step 6115, method 6100 concludes by creating the hierarchical sensornetwork for the grouped set of packages with the mobile master node andthe ID node when the server associates the mobile master node with theID node.

Method 6100 may, in a further embodiment, have the server associate anadditional ID node with one or more of the remaining ones of thepackages; and update the hierarchical sensor network to further compriseeach of the associated additional ID nodes. Thus, such an exemplaryhierarchical sensor network may include more than one ID node and maynot require all of the packages to include a node.

In yet another embodiment, method 6100 may also include having one ormore of the ID nodes shipping condition information related to theirrespective package. Exemplary shipping condition information may, invarious embodiments, include environmental information and locationinformation about a particular ID node (more specifically, the packageassociated with the ID node).

In still another embodiment, the ID node may share the sensed shippingcondition information with the mobile master node. As such, the masternode may then provide the shared sensed shipping condition informationto the server.

And in another embodiment, method 6100 may have the server managingpower consumption of the hierarchical sensor network by transmitting apower management instruction to the master node by the server. The powermanagement instruction causes the mobile master node to alter at leastone operation of the mobile master node and the ID node to change powerconsumption by at least one of the mobile master node and the ID node.For example, the mobile master node may be able to shift to a lowerpower state for a period of time while the ID node is gathering dataonly one a periodic basis (e.g., turning on, gathering sensor data,turning off, turning on again after a set period of time, gathering moresensor data, then turning off again, and so on).

Those skilled in the art will appreciate that method 6100 as disclosedand explained above in various embodiments may be implemented on aserver (such as exemplary server 100 as illustrated in FIGS. 5, 60A, and60B) running one or more parts of a control and management code (such ascode 525) to implement any of the above described functionality. Suchcode may be stored on a non-transitory computer-readable medium (such asmemory storage 515 in an exemplary server). Thus, when executing suchcode, a processing unit of the server (such as unit 500) may beoperative to perform the various steps as disclosed above.

While FIG. 61 illustrates exemplary steps for creating a hierarchicalsensor network from the perspective of exemplary server operations andthe above description expands upon that, FIG. 62 is a flow diagramillustrating an exemplary method of master node operations when creatinga hierarchical sensor cloud for a grouped set of packages being shippedin accordance with an embodiment of the invention. Referring now to FIG.6200, method 6200 begins at step 6205 with the mobile master nodeassociating with one of the packages in the grouped set of packages withthe mobile master node. Here, the mobile master node is operative tocommunicate directly with the server over a longer range communicationpath and operative to communicate with the ID node over a short rangecommunication path.

In one embodiment, the grouped set of packages may comprise a palletizedgroup of packages being shipped together where in another embodimentthey may comprise a group of packages together within a shippingcontainer.

At step 6210, the mobile master node detects a signal broadcast from theID node over the short range communication path (such as a Bluetooth®enabled limited RF communication range). The ID node is associated withanother of the packages in the grouped set of packages, and is operativeto communicate directly with the mobile master node over the short rangecommunication path but not operative to communicate directly with theserver.

At step 6215, the mobile master node transmits an authorization requestto associate the mobile master node and the ID node. And at step 6220,the mobile master node receives a response from the server to authorizeassociating the mobile master node and the ID node.

Finally, at step 6225, method 6200 establishes the hierarchical sensornetwork for the grouped set of packages with the mobile master node andthe ID node when the mobile master node associates with the ID node.

In another embodiment, method 6200 may also include having the mobilemaster node associating an additional ID node with each of the remainingones of the packages, wherein the hierarchical sensor network furthercomprises each of the associated additional ID nodes. Additionalembodiments may include less than all of the remaining ones of thepackages being associated with ID nodes.

In a further embodiment of method 6200, the mobile master node mayreceive shipping condition information from the ID node. In more detail,the shipping condition information may comprise at least one ofenvironmental information (such as temperature, humidity, light, etc.)and location information related to the ID node. Further still, anotherembodiment of method 6200, the mobile master node may provide the sharedshipping condition information received from the ID node to the server.

In yet another embodiment, method 6200 may also include having themobile master node receiving a power management instruction from theserver. The mobile master node may implement the power managementinstruction to manage power consumed by the mobile master node and theID node. For example, the mobile master node may instruct the ID node toalter an operation of the ID node in order to change the power consumedby the ID node. In another example, the mobile master node may alter anoperation of the mobile master node in order to change the powerconsumed by the mobile master node.

Those skilled in the art will appreciate that method 6200 as disclosedand explained above in various embodiments may be implemented on amobile master node (such as exemplary master node 110 a as illustratedin FIG. 4, and master node 6110 a in FIGS. 60A, and 60B), running one ormore parts of a control and management code (such as code 425) toimplement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium (such as memorystorage 415 in an exemplary mobile master node). Thus, when executingsuch code, a processing unit of the master node (such as unit 400) maybe operative to perform operations or steps from the exemplary methodsdisclosed above, including method 6200 and variations of that method.

In addition to aspects involving the internal operations of the serverand mobile master node, an embodiment may create an exemplaryhierarchical sensor network as a way of putting such a network togetherand enabling it. Specifically, FIG. 63 is a flow diagram illustrating anexemplary method of creating a hierarchical sensor network for a groupedset of packages being shipped in accordance with an embodiment of theinvention. Referring now to FIG. 63, method 6300 begins at step 6305 byplacing the mobile master node within one of the packages in the groupedset of packages. Here, the mobile master node is operative tocommunicate directly with a server in the wireless node network over afirst communication path (such as a longer range communication path). Incontrast, the ID node is operative to communicate directly with themaster node over a second communication path (such as a shorter rangecommunication path) but is not operative to communicate directly with aserver over the first communication path.

In one embodiment, the grouped set of packages may comprise a palletizedgroup of packages being shipped together while in another embodimentthey may comprise a group of packages together within a shippingcontainer.

At step 6310, method 6300 continues by placing an ID node within anotherof the packages in the grouped set of packages. At step 6315, method6300 enables the mobile master node and the ID node with power. And atstep 6320, method 6300 concludes by activating the hierarchical sensornetwork for the grouped set of packages by causing the server toassociate the mobile master node with the ID node.

In a further embodiment, method 6300 may also place an additional IDnode within each of the remaining ones of the packages, and enable eachof the additional ID nodes placed within each of the remaining ones ofthe packages. Thus, the enabled each of the additional ID nodes ispowered and discoverable by the mobile master node and added to thehierarchical sensor network when the enabled each of the additional IDnodes is associated with the mobile master node.

In still another embodiment, method 6300 may place an additional ID nodewithin a remaining one of the packages and enable the additional ID nodeplaced within the remaining one of the packages. Thus, the enabledadditional ID node is powered and discoverable by the mobile master nodeand added to the hierarchical sensor network when the enabled additionalID node is associated with the mobile master node

And in yet another embodiment, method 6300 may also include selectingthe packages in the grouped set of packages as a monitored group ofpackages to be shipped together for at least a portion of a shippingpath from an origin to a destination

From a system perspective, an embodiment is described of a hierarchicalsensor system for a set of packages being shipped. The system generallycomprises a mobile master node and a plurality of ID nodes. The mobilemaster node is associated with one of the packages in the set ofpackages. The mobile master node is operative to communicate with aserver over a longer range communication path.

Each of the ID nodes in the system is associated with one of theremaining packages in the set of packages and includes a sensor thatcollects shipment condition information (e.g., environmentalinformation, location information). And each of the plurality of IDnodes is operative to communicate with the mobile master node over ashort range communication path but unable to directly communicate withthe server.

In another embodiment, the mobile master node may further comprise asensor that collects shipment condition information about the one of thepackages in the set of packages. Thus, different embodiments may deployone or more sensors as part of the mobile master node or any of the IDnodes that may make up the hierarchical sensor system.

The mobile master node in the system is further operative to receive thecollected shipment condition information from the ID nodes over theshort range communication path and update the server over the longerrange communication path with summary shipment condition informationrelated to each of the packages in the set of packages, the summaryshipment condition information being based upon the collected shipmentcondition information from the ID nodes. For example, such summaryshipment condition information may be a compilation of environmental andlocation information collected related to packages in the set ofpackages.

In a further embodiment, the set of packages may comprise a group ofpackages identified by shipping information to be related and shippedtogether, where the shipping information is maintained on the server anddefined by a shipping customer. This allows for a more personalselection of which packages may make up the group of packages, and allowmore flexibility and visibility for tracking purposes to a shippingcustomer. And those skilled in the art will appreciate that the set ofpackages may, in some embodiments, comprise a palletized group ofpackages being shipped together while, in other embodiments, comprise agroup of packages together within a shipping container (such as a ULD).

Autonomous Node-Enabled Vehicle Logistics Applications

Exemplary elements of a wireless node network may also be applied inembodiments involving autonomous vehicle transports that are able topick-up, carry, hand-off, and deliver packaged items as part of anexemplary logistics system. By incorporating a mobile master node intothe autonomous vehicle, and using other nodes at different locations, anembodiment of the mobile master node may be able to manipulate andcontrol the other nodes so as to navigate to a shipping location or,more generally, a waypoint (e.g., a pickup point, a drop-off point, or adelivery point) along an anticipated transit route for a packaged item.

Node-Based Navigation for Autonomous Transport Vehicles

FIGS. 67A-67D are diagrams illustrating an exemplary node-enabledtransport vehicle in various stages of navigating using nodes in awireless node network in accordance with an embodiment of the invention.Referring now to FIG. 67A, an exemplary node-enable transport vehicle isillustrated based upon an autonomous vehicle 6700. Examples of such anautonomous vehicle may be implemented as a pilotless, driverless, orunmanned means of transportation, such as a drone, automobile, truck,bus, tractor, aerial vehicle, railway vehicle, or marine vehicle. Thevehicle 6700 may be implemented in a variety of sizes that may dependupon, for example, the types of packages to be transported, theenvironment in which the vehicle 6700 will be running (e.g., inside,outdoors), the accuracy required in movement (e.g., width foroperations, turn around spacing, etc.), and the anticipated payload andarticulating loading and unloading mechanisms (e.g., robotic arms,cranes, drop-down conveyor belts to help load and unload packages,etc.).

As shown in FIG. 67A, the exemplary autonomous vehicle 6700 incorporatesa master node 6725 and employs a control system 6705 and sensors 6722 tonavigate from one location to another location via a propulsion system6710 and a steering system 6715 while carrying packages in a packagepayload. The master node 6725 (e.g., node 400 as shown and described inFIG. 4) is operative to communicate with server 100 over a longer-rangecommunication interface (e.g., interface 485 as shown on master node 110a in FIG. 4). In one embodiment, the master node 6725 may be integratedinto and be part of a processor-based system within the electronicsonboard autonomous vehicle 6700. In another embodiment, the master node6725 may be implemented as a standalone separate unit that may be addedand/or fixed to a part of the autonomous vehicle 6700 (e.g., a storagecompartment, a weather sealed compartment, etc.). Additionally, whilenode 6725 appears as a master node in FIGS. 67A-67D, other embodimentsmay implement node 6725 as an ID node. Further still, there may beembodiments where node 6725 associated with the autonomous transportvehicle may be implemented a master node temporarily operating as an IDnode (e.g., as in when a master node can no longer self-determine itsown location).

Those skilled in the art will appreciate that, depending upon theimplementation of the autonomous vehicle 6700 (e.g., an autonomoustruck, an unmanned autonomous flying drone quad-copter, an autonomousrailway vehicle), the types of control systems 6705, propulsion systems6710, steering systems 6715, and onboard sensors 6722 will vary in orderto successfully have the vehicle 6700 navigate to a location on its ownpower and control. For example, an autonomous railway vehicle may beimplemented with a hybrid diesel electric propulsion system in order totow a large number of railcars having a vast package payload, but with asimple steering system given the implementation. In another example, anautonomous quad-copter drone vehicle may have four motors or engines asits collective propulsion system and have a more advanced steeringsystem given the larger number of actuators used to fly such an aerialvehicle in stable flight.

Exemplary sensors 6722 on vehicle 6700 are typically used to help guidethe vehicle 6700 when moving and avoid obstacles. For example, oneembodiment may use ultrasonic sensors to detect objects in closeproximity (e.g., walls, curbs, doors, packages, etc.). Other examples ofsensors may include RADAR, LiDAR (using a laser to illuminate an objectand analyzing the reflected light), computer vision with imageprocessing and recognition, infrared sensors (e.g., forward lookinginfrared or FLIR technology), and the like. Those skilled in the artwill appreciate that such sensors may scan and create useful images andmaps to help avoid obstacles.

Exemplary control system 6705 is disposed within or on the autonomousvehicle 6700. The control system 6705 has the capacity to sense itsenvironment as input, navigate between locations, and control propulsionand steering in response to the sensed and navigation inputs. Thecontrol system 6705 has a collective output coupled to the control inputof the autonomous vehicle (e.g., inputs to the propulsion system 6710and steering system 6715). In more detail, the exemplary control system6710 further has at least one input for receiving an instruction on adesired movement for the autonomous vehicle (e.g., control instructionsto start/stop the vehicle, accelerate or slow down the vehicle, turn thevehicle, and make the vehicle go in a particular direction (e.g.,forward, backward, left, right, up, down) and produces a control signalon the output responsive to the instruction received.

In some embodiments, control system 6705 may also include guidanceequipment, such as a compass, gyroscope, accelerometer, inertialsensors, GPS receiver circuitry, and the like. In one example, thecontrol system may include an inertial navigation system (not separatedshown in FIG. 67A) that is capable of operating in hostile RFenvironments (e.g., indoors, within shielded facilities, underwater,etc.).

As shown in FIG. 67A, master node 6725 is a mobile master node onboardautonomous vehicle 6700, which is capable of moving under its owncontrol and propulsion from one location to another location in responseto control input. Additionally, FIG. 67A shows various ID nodes 6735a-6735 c at different locations relative to vehicle 6700. In oneembodiment, the ID nodes may operate by broadcasting advertising signalsto help the node-enabled autonomous vehicle 6700 navigate. Generally,the mobile master node 6725 is able to identify an ID node at a desiredlocation (e.g., a waypoint along an anticipated route for packagepickup, transport, or delivery), associate with that ID node, instructthat ID node to lower the broadcasting power, and determine a directionwhere the ID node is located based on sensing the lowered broadcastingpower. The gradual or incremental lowering of ID node output power helpsto indicate where the ID node is located and where the mobile masternode should be headed. This may be repeated for the next waypoint in aseries of waypoints.

In more detail, FIG. 67A illustrates ID node 6735 a within package 6740at a shipping location 6730 (e.g., a front door, a shipping dock, astorage room) with other ID nodes (such as ID nodes 6735 b, 6735 c) inthe general area. ID node 6735 a is broadcasting an advertising signalat a high power, which corresponds to a larger broadcast range 6745 a.Upon detecting this signal from ID node 6735 a, mobile master node 6725in vehicle 6700 may instruct ID node 6735 a to lower the broadcastoutput power. Thus, as shown in FIG. 67B, mobile master node 6725 maydetect that ID node 6735 a has lowered its output signal to a lowerpower 6745 b, which then allows mobile master node to determine ageneral direction of the ID node 6735 a and move in that direction(e.g., provide the determined direction as an input to control system6705, which controls movement and steering through propulsion system6710 and steering system 6715). Thus, mobile master node 6725 and the IDnode 6735 a may be used to help guide and navigate when the vehicle 6700needs to move to the shipping location 6730 to pick-up one or morepackages there, drop off one or more packages there, or simply use thatlocation 6730 as a waypoint so that vehicle 6700 can then move on to thenext waypoint in an anticipated route and ultimately get to its desireddestination.

In some embodiments, the node-enabled autonomous vehicle 6700 may use acentral courier vehicle (e.g., truck, van) as a type of base from whichto make runs to different addresses to pick up one or more packages forshipment, or drop off one or more packages for delivery. In such anembodiment, the central vehicle from which the node-enabled autonomousvehicle 6700 departs and returns may include a ramp or otherarticulating loading and unloading mechanisms (e.g., robotic arms,cranes, drop-down conveyor belts to help load and unload the variousautonomous vehicles as they leave and return to the central vehicle,etc.).

In other embodiments, the node-enabled autonomous vehicle 6700 may ferryone or more packages from one location (such as a courier vehicle) toanother location (such as another courier vehicle). In still otherembodiments the node-enabled autonomous vehicle 6700 may ferry ortransport packages between storage locations in a shipping facility oroff a truck and into an entrance of a sorting facility using exemplaryarticulating loading and unloading mechanisms (e.g., robotic arms,cranes, drop-down conveyor belts to help load and unload packages,etc.).

FIG. 67C illustrates an embodiment where the ID nodes may be used as aseries of waypoints. Referring now to FIG. 67C, vehicle 6700 may havearrived near ID node 6735A (as shown and explained with respect to FIGS.67A and 67B), but now is moving on to another waypoint at ID node 6735 e(and then ID nodes 6735 f, 6735 g, and 6735 h as further waypoints inthe series). Mobile master node 6725 embedded in node-enabled autonomousvehicle 6700 may instruct ID node 6735 e to lower its output signal 6750so that the master node 6725 can identify a direction towards that IDnode and cause the vehicle 6700 to move in that direction.

FIG. 67D illustrates a further embodiment where an exemplarynode-enabled autonomous vehicle 6700 has an anticipated route that willtake it through a corridor 6760 and towards a conveyor system 6765within a shipping facility (such as a package sorting facility). In thisexample and within such a facility, the exemplary node-enabledautonomous vehicle 6700 may transport packages to be placed onto theconveyor system 6765 for processing, scanning, sorting, and furtherdistribution logistics activities. In doing so, the node-enabledautonomous vehicle 6700 is able to navigate along the anticipated routevia waypoint associated with broadcasting ID nodes along the way. Forexample, as node-enabled autonomous vehicle 6700 approaches the entranceto corridor 6760, mobile master node 6725 within vehicle 6700 may detectan advertising signal 6750 being broadcast from ID node 6735 e.Additionally, mobile master node 6725 may rely on and use context dataabout the corridor and the surrounding anticipated environment to betternavigate from ID node to ID node along the route. Such exemplary contextdata relates to the anticipated operating environment of the IDnode—e.g., mobile master node 6725 may access context data identifyingthat corridor 6760 is dimensionally 75 feet long and 10 feet wide andprovide layout information for the corridor (e.g., turns along the way,etc.). Proximity data may also be gathered from sensors 6722 as thevehicle 6700 moves along the route from ID node to ID node (each ofwhich may be managed and associated with different master nodes 6770before they associate with and are controlled by mobile master node6725). Thus, as the mobile master node 6725 controls the respective IDnodes along the route, the broadcast characteristics of the different IDnodes may be detected by the mobile master node 6725 such that itnavigates towards a final destination (e.g., a loading area for conveyorsystem 6765).

FIG. 68 is a flow diagram illustrating an exemplary method fornavigating to a shipping location by an autonomous transport vehicleusing a plurality of nodes in a wireless node network in accordance withan embodiment of the invention. Referring now to FIG. 68, method 6800begins at step 6805 with a mobile master node associated with theautonomous transport vehicle detecting a signal broadcast from an IDnode associated with the shipping location. The mobile master node isone of the plurality of nodes and can communicate directly with a serverin the wireless node network over a first communication path. The IDnode is another of the plurality of nodes and can communicate directlywith the mobile master node over a second communication path but is notable to communicate directly with the server over the firstcommunication path.

In one embodiment, method 6800 may also include the mobile master nodereceiving an identification of the ID node from the server. For example,server 100 may have anticipated or predicted a route using one or moreID nodes and transmit an identification (e.g., a MAC address or otheridentifier) associated with ID node 6735 a shown in FIG. 67A. In thisembodiment, the detecting step may comprise detecting the identificationof the ID node from the signal broadcast from the ID node.

In one embodiment, the shipping location may comprise one from a groupconsisting of a delivery point, a drop-off point, and a pickup point. Inanother example, the shipping location may be a waypoint in ananticipated route. In a more detailed example, the shipping location maybe implemented as a first waypoint of a plurality of waypoints on ananticipated route as the mobile master node approaches a transitdestination for a package transaction. Each of the plurality ofwaypoints is associated with a different ID node. For example, as shownin FIG. 67C, different waypoints may be associated with different onesof ID nodes 6735 e, 6735 f, 6735 g, and 6735 h.

At step 6810, method 6800 has the mobile master node instructing the IDnode to lower a power level of the signal broadcast from the ID node.For example, mobile master node 6725 in FIG. 67A instructs ID node 6735a to lower the power level 6745 a of the signal being broadcast, whichis then shown at the lowered power level 6745 b in FIG. 67B.

At step 6815, the mobile master node identifies the signal broadcastfrom the ID node with the lowered power level. In this way, the ID nodecan be distinguished from other ID nodes broadcasting in the area aroundthe node-enabled autonomous vehicle 6700 having mobile master node 6725.

At step 6820, the mobile master node determines a direction of the IDnode relative to the mobile master node based upon the detected signalwith the lowered power level. The mobile master node, for example, isable to distinguish the ID node broadcasting the lower power levelsignal and determine a direction towards that ID node.

At step 6825, the mobile master node navigates to the ID node associatedwith the shipping location based upon the determined direction. In oneembodiment, such navigation may be accomplished by navigating to the IDnode as the power level of the signal is incrementally decreased overtime as the mobile master node approaches the ID node.

In another example where the mobile master node is associated with acontrol system of an autonomous vehicle transport (such as controlsystem 6705 of node-enabled autonomous vehicle 6700), such navigatingmay be accomplished when the mobile master node provides the determineddirection to an input of the control system to cause the autonomousvehicle transport to stop moving when a current location of the mobilemaster node is within a predetermined range of the ID node.

In a more detailed example, navigating may be accomplished by firstaccessing context data that relates to an operating environment of theID node, and then navigating to the ID node referencing the accessedcontext data as the power level of the signal is incrementally decreasedover time and as the mobile master node approaches the ID node. Forexample, the referenced context data may provide layout and dimensionalinformation along the anticipated route of the vehicle as it approachesthe ID node.

In a still more detailed example, navigating may be accomplished byfirst accessing context data that relates to an anticipated operatingenvironment of the ID node, gathering proximity sensor data from atleast one sensor deployed on the autonomous vehicle transport, and thennavigating to the ID node with reference to the accessed context dataand the proximity sensor data as the power level of the signal isincrementally decreased over time and as the mobile master nodeapproaches the ID node. In such an embodiment, the operating environmentof the ID node may be within a shipping facility, such as a packagesorting facility (such as the exemplary facility illustrated in FIG. 67Dhaving a corridor 6760 and a conveyor system 6765 where node-enabledautonomous vehicle 6700 may navigate through corridor 6760 usingwaypoints of ID nodes before dropping off one or more packages at theconveyor system 6765.

Method 6800 may also, in a further embodiment, have the mobile masternode transmit an updated location of the mobile master node to theserver as the mobile master node approaches the ID node. The updatedlocation of the mobile master node may be determined using locationcircuitry (such as a GPS chipset and antenna) on the mobile master node.

In another example, the mobile master node may be associated with acontrol system of an autonomous vehicle transport, such that the updatedlocation of the mobile master node is determined based at least in partupon a determined position from an inertial navigation unit deployed onthe autonomous vehicle transport. In still another example, the updatedlocation of the mobile master node may be determined based upon anonboard location provided by location circuitry on the mobile masternode (such as the GPS chipset and antenna) when available and, when theonboard location is not available, the updated location of the mobilemaster node may be determined based at least in part upon a determinedposition from an inertial navigation unit deployed on the autonomousvehicle transport. Thus, an embodiment provides the capability tonavigate within a facility and indoors when GPS signals may be lost.

Those skilled in the art will appreciate that method 6800 as disclosedand explained above in various embodiments may be implemented on amobile master node (such as exemplary master node 110 a as illustratedin FIG. 4, and master node 6725 in FIGS. 67A-67D), running one or moreparts of a control and management code (such as code 425) to implementany of the above described functionality. Such code may be stored on anon-transitory computer-readable medium (such as memory storage 415 inan exemplary mobile master node). Thus, when executing such code, aprocessing unit of the master node (such as unit 400) may be operativeto perform the various steps as disclosed above.

Furthermore, another embodiment includes a node-enabled transportvehicle. The transport vehicle comprises an autonomous vehicle operativeto move from an initial location to a shipping location in response tocontrol input. The shipping location may be, for example, a deliverypoint, a drop-off point, a pickup point, a waypoint in an anticipatedroute for the autonomous vehicle, or a first waypoint of a plurality ofwaypoints on an anticipated route as the vehicle approaches a transitdestination for a package transaction.

The transport vehicle further comprises a control system disposed on theautonomous vehicle. The control system (e.g., control system 6705 shownin FIGS. 67A-67D) has an output coupled to the control input of theautonomous vehicle (such as the input to propulsion systems 6710 andsteering system 6715). The control system further has at least one inputfor receiving an instruction on a desired movement for the autonomousvehicle and producing a control signal on the output responsive to theinstruction received.

The transport vehicle further comprises a mobile master node associatedwith it. The mobile master node is one of a plurality of nodes in awireless node network that can communicate directly with a server in thenetwork. As described above, the mobile master node may, in oneembodiment, be integrated into one of the processor-based electronicsystems onboard the autonomous vehicle. But in another embodiment, themobile master node may be a standalone unit attached or otherwisephysically associated with the vehicle. The mobile master node providesa directional output signal as an instruction to the input of thecontrol system.

In more detail, the mobile master node comprises a node processing unit,node memory, and a short-range and longer range communicationinterfaces. The node memory is coupled to the node processing unit andat least maintains code for execution by the node processing unit, aswell as data generated during operation of the mobile master node. Theshort-range communication interface is coupled to the processing unitand can communicate with an ID node associated with the shippinglocation. The ID node is another of the plurality of nodes and cancommunicate directly with the mobile master node over the short-rangecommunication interface but is unable to communicate directly with theserver in the network. The longer range communication interface iscoupled to the node processing unit and provides the means tocommunicate directly with the server.

The node processing unit of the mobile master node, when executing thecode maintained on the node memory, is operative to perform steps andoperations as described and set forth above with respect to FIG. 68 andmethod 6800. In more detail, the node processing unit is operative, assuch, to detect, over the short-range communication interface, a signalbroadcast from the ID node associated with the shipping location. Thenode processing unit is operative to transmit an instruction over theshort-range communication interface to the ID node, where theinstruction causes the ID node to lower a power level of the signalbroadcast from the ID node. An example of this is illustrated in FIGS.67A and 67B where the power levels are initially at a higher level 6745a but are changed to a lower level 6745 b.

The node processing unit is then operative to identify the signalbroadcast from the ID node with the lowered power level, determine adirection from the mobile master node to the ID node based upon thedetected signal with the lowered power level, and provide the determineddirection as the instruction to the input of the control system.

In a further embodiment of the node-enable transport vehicle, the nodeprocessing unit may be further operative to determine the direction tothe ID node and provide the determined direction as the directionaloutput signal as the power level of the detected signal broadcast fromthe ID node is incrementally decreased over time and as the mobilemaster node approaches the shipping location.

In yet another embodiment, the node processing unit may be furtheroperative to receive an ID node identification from the server over thelonger range communication interface. Here, the ID node identificationis related to the ID node associated with the shipping location and thenode processing unit may be further operative to detect the ID nodeidentification of the ID node associated with the shipping location fromthe signal broadcast from the ID node associated with the shippinglocation.

In another embodiment, the node processing unit may be further operativeto instruct the control system based upon the directional input to causethe autonomous vehicle transport to stop moving when a current locationof the mobile master node is within a predetermined range of the ID nodeassociated with the shipping location. In that embodiment, the nodeprocessing unit may be further operative to transmit an update to theserver reflecting that the current location of the mobile master node iswithin the predetermined range of the ID node. Thus, the server isupdated with current location and status information so as to be readyto respond to requests for such information.

In still another embodiment, context data may be used with anode-enabled transport vehicle to provide enhanced navigation abilities.In particular, an embodiment may have the node memory maintainingcontext data with the node processing unit being further operative toaccess a part of the context data that relates to an operatingenvironment (more specifically, an anticipated operating environment) ofthe ID node. The node processing unit may be further operative todetermine the direction to the ID node with reference to the accessedcontext data as the power level of the signal is incrementally decreasedover time and as the mobile master node approaches the ID node.

In another embodiment of the node-enabled transport vehicle, theautonomous vehicle may further comprises at least one sensor disposed onthe autonomous vehicle and coupled at least to the node processing unitof the mobile master node (or, alternatively, coupled to the controlsystem on the autonomous vehicle). In this embodiment, which alsoleverages the use of context data, the node processing unit may befurther operative to access a part of the context data that relates toan anticipated operating environment of the ID node, gather proximitydata from the at least one sensor, and determine the direction to the IDnode with reference to the accessed context data and the proximitysensor data as the power level of the signal is incrementally decreasedover time and as the mobile master node approaches the ID node. Thus,the autonomous vehicle may be navigating with the advantage of referringto the sensed proximity of the vehicle, an anticipated operativeenvironment of the ID node where they are and are headed, and with adirection determined based on the changing ID node broadcast powerlevels detected. Further, the operating environment of the ID node maybe within a shipping facility, such as a package sorting facility.

In a further embodiment, the node-enabled transport vehicle (morespecifically, the mobile master node within the vehicle) may be able toprovide location information for the vehicle to the server. In oneembodiment, the mobile master node may include onboard locationcircuitry (such as a GPS chipset and antenna) coupled to the nodeprocessing unit such that the unit may be further operative to obtain anupdated location of the mobile master node from the onboard locationcircuitry, and transmit the updated location over the longer rangecommunication interface to the server as the mobile master nodeapproaches the shipping location.

In another embodiment, the vehicle may also include an inertialnavigation unit deployed on the autonomous vehicle that generates adetermined position for the location of the autonomous vehicle. Forexample, an exemplary inertial navigation unit may use accelerometers,gyroscopes, magnetometers, and/or pressure sensors as part ofdetermining a position based upon such sensors. In this embodiment, thenode processing unit may be further operative to determine an updatedlocation of the mobile master node at least in part on the determinedposition obtained from the inertial navigation unit, and transmit theupdated location over the longer range communication interface to theserver.

In an embodiment having both onboard location circuitry in the mobilemaster node and the inertial navigation unit, the node processing unitmay be further operative to determine if an updated location of themobile master node from the onboard location circuitry is available. Ifso, it can transmit to the server over the longer range communicationinterface the updated location obtained from the onboard locationcircuitry. However, it can transmit to the server over the longer rangecommunication interface the determined position obtained from theinertial navigation unit if the updated location is not available. Thus,a more robust ability to operate in outdoor and indoor environments isprovided.

In still another embodiment where there are a number of waypoints (eachof which are associated with an ID node), the node processing unit maybe further operative to detect, over the short-range communicationinterface, a signal broadcast from the another ID node associated with anext of the waypoints. The node processing unit may be then operative totransmit an instruction over the short-range communication interface tothe other ID node, where the instruction causes the other ID node tolower a power level of the signal broadcast from the another ID node.The node processing unit may then be operative to identify the signalbroadcast from the other ID node with the lowered power level, determinea further direction on the anticipated route from the mobile master nodeto the other ID node based upon the detected signal with the loweredpower level broadcast from the other ID node, and provide the determineddirection on the anticipated route as the instruction to the input ofthe control system.

Autonomous Vehicle Package Transactions with Nodes

The use of an autonomous vehicle for package pickup and delivery (e.g.,types of logistics transactions for a package) may be further enhancedusing nodes in a wireless node network. FIG. 69A is a diagramillustrated an exemplary courier transport vehicle having an exemplarynode-enabled autonomous vehicle in accordance with an embodiment of theinvention. Referring now to FIG. 69A, exemplary node-enabled autonomousvehicle 6700 is shown within a courier transport vehicle 6910 that maybe used to transport one or more packages (not shown) within vehicle6910 for delivery at various locations or for simply ferrying suchpackages between locations. The advantageous use of a node-enabledautonomous vehicle, such as vehicle 6700, to assist withloading/unloading of vehicle 6910 as well as carrying out logisticstransactions, such as picking up a package from a designated address ordelivering a package to such an address may allow for a more efficientlogistics system in an embodiment.

Exemplary node-enabled autonomous vehicle 6700 is shown in thisillustrated embodiment more particularly includes an exemplary packagearticulation system having an electronic module 6900, which is connectedto and controls an articulating system 6905 movable to place and removea package from within the package payload storage 6720 of vehicle 6700.In one embodiment, the module and system may be implemented with arobotic arm having multiple degrees of freedom so as to provide greaterflexibility in loading and unloading packages proximate to the vehicle6700. However, those skilled in the art will appreciate that otherembodiments of a package articulation system may be implemented using,for example, loading conveyors, multiple grasping extensions or armsfrom vehicle 6700, a loading platform that articulates down to anadequate level to help capture a package, and the like. Likewise, theend of articulating system 6905 is illustrated as having articulatingcontact points that can grasp a package, but other embodiments may usedifferent types of structure to articulate and maintain a grasp andcontrol of a package as it is placed in or removed from the packagepayload 6720.

In one embodiment, courier transit vehicle 6910 has a courier transitvehicle mobile master node 6915, such as that illustrated in FIG. 69ASuch a master node 6915 on board the vehicle 6910 allows master node6915 to more efficiently manage and report on packages picked up anddelivered as well as deliver shipment information to the node-enabled.However, other embodiments may have master node 6725 in autonomousvehicle 6700 be responsible for downloading shipping information onpackages that are subject to logistics transactions, such as pickingthem up or dropping them off.

Autonomous vehicle 6700 may be deployed from the courier transportvehicle 6910 and travel to and from a transaction location (e.g., apickup location, address, designated area for dropping off packages, andthe like) where the vehicle 6700 may pick up or drop off a package.Depending on how the exemplary autonomous vehicle 6700 and the exemplarycourier transport vehicle 6910 are configured and the particularapplication details (e.g., how big and how many packages may betransported by each, etc.), deploying the autonomous vehicle 6700 may beaccomplished by, for example, simply opening a back or side door ofcourier transport vehicle 6910. In another embodiment, autonomousvehicle 6700 may be quickly deployed from a dedicated launch bay (notshown) of courier transport vehicle 6910 where vehicle 6910 may includededicated hardware to assist gather packages that have been brought tothe vehicle 6910 during a pickup logistics transaction or to assetloading on or more packages from a storage area on vehicle 6910.

FIG. 69B is a diagram illustrated the exemplary node-enabled autonomousvehicle as it approaches a package and related ID node for an exemplarylogistics transaction at a transaction location in accordance with anembodiment of the invention. Referring now to FIG. 69B, the autonomousvehicle 6700 has been deployed and approaches package 6740 having IDnode 6735 a within it. The package 6740 is located at a location oraddress, generally referred to as a transaction location 6920 for thepackage. In this example, the package 6740 is awaiting pickup and ashipping customer may have entered a shipment order where shippinginformation related to the order is maintained on the server 100. Theautonomous vehicle 6700 would receive such shipping information so thatit knows what package to pick up, where the pickup logistics transactionshould take place, and an identification of any ID node associated withthe package. Armed with that information, the mobile master node 6725within autonomous vehicle 6700 is then operative to control how theautonomous vehicle 6700 automatically conducts the logisticstransaction.

In another example, those skilled in the art will appreciate a similartype of operation takes place when the autonomous vehicle 6700 isdeployed to conduct a drop off logistics transaction where the packageis ferried by the vehicle 6700 to the transaction location 6920 and thenremoving the package from the package payload 6720 and placing thepackage at the location 6920 to deliver the package.

FIG. 70 is a flow diagram illustrating an exemplary method forautomating a logistics transaction using a plurality of nodes and aserver in a wireless node network in accordance with an embodiment ofthe invention. Referring now to FIG. 70, method 7000 begins at step 7005where a first of the nodes (a node associated with a shipping courier)downloads shipment information from the server. The shipment informationidentifies a package for the logistics transaction, a transactionlocation for the logistics transaction, and an identification of asecond of the nodes associated with the package.

At step 7010, the first node provides the shipment information to athird of the nodes, wherein the third node is part of an autonomousvehicle. For example, as shown in FIG. 69A, courier transport vehiclemaster node 6915 may receive and download shipping formation on apackage to be picked up (if the logistics transaction is a pick upoperation for autonomous vehicle 6700) from server 100, and then providethat shipping information to mobile master node 6725 in vehicle 6700. Inanother embodiment, the embedded mobile master node 6725 may directlydownload the shipping information from server 100.

At step 7015, the third node causes the autonomous vehicle to move froman initial location (more generally referred a first location) to thetransaction location. For example, as shown in FIG. 69B, mobile masternode 6725 in autonomous vehicle 6700 may operate as the third node andcauses vehicle 6700 to move from an initial deployment location outsideof courier transport vehicle 6910 to a transaction location 6920identified in the shipping information. This may be done withinstructions and signals provided from node 6725 to control system 6705,which then manages operations of the propulsion system 6710 and steeringsystem 6715.

At step 7020, method 7000 concludes when the third node conducts thelogistics transaction related to the package if the third node on theautonomous vehicle completes a node association with the second nodeassociated with the package. As explained above, generally a logisticstransaction is a type of operation involving any logistics stage ofshipping, such as picking up the package of interest, ferrying thepackage of interest between locations, dropping off the package ofinterest, moving the package of interest, etc.

In one embodiment where the logistics transaction comprises picking upthe package at the transaction location after the third node associateswith the second node, conducting the logistics transaction may be donewhen the third node detects a signal from the second node (associatedwith the package) as the autonomous vehicle approaches the transactionlocation. Thereafter, the conducting step may continue when the thirdnode and the second node are associated, the package is picked up at thetransaction location, and then placed into a package payload storage ofthe autonomous vehicle.

In this embodiment, method 7000 may also comprise returning, by theautonomous vehicle, to the courier transport vehicle to unload thepackage and the second node from the package payload storage of theautonomous vehicle, and then transmit a verification message to theserver. The verification message confirms that the package was picked upand is on the courier transport vehicle.

In another embodiment where the logistics transaction comprises droppingoff the package at the transaction location after the third nodeassociates with the second node, conducting the logistics transactionmay be done when the third node detects a signal from the second node asthe autonomous vehicle approaches the transaction location. Thereafter,the conducting step may continue when the third node and the second nodeare associated, the package is removed from a package payload storage ofthe autonomous vehicle; and the autonomous vehicle is controlled to dropoff the package at the transaction location.

In this embodiment, method 7000 may have deployed the autonomous vehiclefrom a courier transport vehicle at the initial location, and had thepackage loaded into a package payload storage of the autonomous vehicleprior to causing the autonomous vehicle to move from the initiallocation to the transaction location.

And still in this embodiment, method 7000 may also cause the autonomousvehicle to return to the courier transport vehicle; and transmit averification message to the server, where the verification messageconfirms that the package was dropped off at the transaction locationand is no longer on the courier transport vehicle.

In a more detailed embodiment, the first node and the third node mayeach be a mobile master node (such as master node 6915 in couriertransport vehicle 6910 and master node 6725 embedded in or integrated aspart of autonomous vehicle 6700. Each of the mobile master nodes is oneof the plurality of nodes and is operative to communicate directly withthe server in the wireless node network over a first communication path.In contrast, the second node may be an ID node, where the ID node isanother of the plurality of nodes and is operative to communicate witheach of the master nodes over a shorter range communication path but isunable to communicate directly with the server.

In another embodiment, an exemplary system is described for automating alogistics transaction related to a package. The system generallycomprises three nodes—a first node associated with a courier transportvehicle, a second node associated with the package, and a third nodeintegrated as part of an autonomous vehicle related to the couriertransport vehicle. Examples of such nodes in an illustrated embodimentappear as master node 6915 associated with a courier transport vehicle6910, ID node 6735 a associated with the package 6740, and mobile masternode 6725 integrated as part of an autonomous vehicle 6700 related tothe courier transport vehicle 6910 as shown in FIGS. 69A and 69B.

In the system, the first node is operative to download shipmentinformation from the server. The shipment information identifies thepackage for the logistics transaction, a transaction location for thelogistics transaction related to the package, and an identification ofthe second node associated with the package. The first node alsoprovides the shipment information to the third node.

And in the system, the third node is operative to cause the autonomousvehicle to move from a first location proximate the courier transportvehicle to the transaction location, and conduct the logisticstransaction related to the package if the third node successfullyassociates with the second node associated with the package.

In an embodiment where the logistics transaction comprises picking upthe package at the transaction location after the third nodesuccessfully associates with the second node, the ability of the thirdnode to conduct the logistics transaction may be explained in moredetail as detecting a signal from the second node associated with thepackage as the autonomous vehicle approaches the transaction location,associating the third node and the second node, instructing a packagearticulation system on the autonomous vehicle to pick up the package atthe transaction location, and instructing the package articulationsystem to place the package in a package payload storage of theautonomous vehicle. Those skilled in the art will appreciate that havingthe third node instruct the package articulation system to perform afunction generally involves providing a control signal to a systemcontrolling the package articulation system (such as control system 6705that controls the load/unload system 6900 and articulating arms 6905 ofthe package articulation system shown in FIGS. 69A and 69B).

In still a further embodiment, the third node may be further operativeto cause the autonomous vehicle to return to the courier transportvehicle, instruct the package articulation system to unload the packageand the second node associated with the package from the package payloadstorage of the autonomous vehicle into a storage area of the couriertransport vehicle, and transmit a verification message to the server,wherein the verification message confirming that the package was pickedup and is on the courier transport vehicle.

In another embodiment where the logistics transaction comprises droppingoff the package at the transaction location after the third nodesuccessfully associates with the second node, the third node may befurther operative to conduct the logistics transaction by being furtheroperative to perform several more detailed operations. Specifically, thethird node may be operative to detect a signal from the second nodeassociated with the package as the autonomous vehicle approaches thetransaction location, associate the third node and the second node,instruct a package articulation system on the autonomous vehicle toremove the package from a package payload storage of the autonomousvehicle, and instruct the package articulation system to drop off thepackage at the transaction location. Thereafter, the third node may befurther operative to transmit a verification message to the server,where the verification message confirms that the package was dropped offat the transaction location.

In a more detailed embodiment of the system, the first node and thethird node may each be implemented as a mobile master node, where eachof the mobile master nodes is one of the plurality of nodes and isoperative to communicate directly with the server in the wireless nodenetwork over a first communication path. And in more detail in thisembodiment, the second node may be an ID node, where the ID node isanother node of the plurality of nodes and is operative to communicatewith each of the master nodes over a shorter range communication pathbut is unable to directly communicate with the server.

While an exemplary system in an embodiment is described above, anotherembodiment involves just a node-enabled autonomous vehicle that conductsa logistics transaction related to a package. In this embodiment, thenode-enabled autonomous vehicle comprises an autonomous vehicle and amobile master node integrated as part of the autonomous vehicle. Theautonomous vehicle is operative to move, in response to control input,from an initial location to a transaction location related to thelogistics transaction. The mobile master node is one of a plurality ofnodes in a wireless node network and further comprises a node processingunit, a node memory, a short-range communication interface and a longerrange communication interface. The node memory, short-rangecommunication interface and longer range communication interface areeach coupled to the node processing unit (such as shown in FIG. 4 forexemplary master node 110 a). The short-range communication interface isoperative to communicate with the nodes in the wireless node network,while the longer range communication interface is operative tocommunicate directly with a server in the wireless network.

The node processing unit of the mobile master node, when executing thecode maintained on the node memory, is operative to perform severalfunctions. In particular, the node processing unit is first operative toreceive shipment information generated by the server. The shipmentinformation identifies the package for the logistics transaction, thetransaction location for the logistics transaction related to thepackage, and an identification of the second node associated with thepackage. The node processing unit is then operative to provide a controlsignal to control input of the autonomous vehicle causing the autonomousvehicle to move from the initial location to the transaction location,and automatically conduct the logistics transaction related to thepackage if the third node successfully associates with the second nodeassociated with the package.

In one embodiment where the logistics transaction may comprise pickingup the package at the transaction location after the third nodesuccessfully associates with the second node, the autonomous vehicle mayfurther comprise a package payload storage and a package articulationsystem that may be operative to place the package within the packagepayload storage and remove the package from within the package payloadstorage. In the example shown in FIGS. 69A and 69B, such a payloadstorage appears as package payload 6720. While shown small in scalerelate to other components in autonomous vehicle 6700, those skilled inthe art will appreciate that the relative size shown in the figures isnot limiting and that the size for such storage may be dictated by thesize of packages anticipated to be transported, the propulsion capacityfor the autonomous vehicle, etc. Likewise, the illustrated packagearticulation system shown in FIGS. 69A and 69B may take a variety ofcontrollable machinery, such as lift gates, robotic arms, articulatingscoops, and the like to capture a package and transport the packagesafely between locations.

In this embodiment here the logistics transaction is picking up thepackage, the third node may be further operative to automaticallyconduct the logistics transaction by being operative to detect a signalfrom the second node associated with the package as the autonomousvehicle approaches the transaction location, associate the third nodeand the second node, and provide a pickup control signal to the controlinput of the autonomous vehicle to cause the package articulation systemon the autonomous vehicle to pick up the package at the transactionlocation and place the package in the package payload storage of theautonomous vehicle.

In a further embodiment, the third node may also be operative to causethe autonomous vehicle to return to the courier transport vehicle. Thismay be accomplished with a movement-related control signal. The thirdnode may also be operative to provide an unload control signal to thecontrol input of the autonomous vehicle to cause the packagearticulation system to unload the package and the second node associatedwith the package from the package payload storage of the autonomousvehicle, and then transmit a verification message to the server over thelonger range communication interface, where the verification messageconfirming that the package was picked up.

In another embodiment where the logistics may comprise dropping off thepackage at the transaction location after the third node successfullyassociates with the second node, the autonomous vehicle may furthercomprise a package payload storage and a package articulation systemoperative to place the package within the package payload storage andremove the package from within the package payload storage.

In this embodiment, the third node may be further operative to conductthe logistics transaction by detecting a signal (e.g., a broadcastadvertising signal) from the second node as the autonomous vehicleapproaches the transaction location, associating the third node and thesecond node, and providing a drop off control signal to the controlinput of the autonomous vehicle. The drop off control signal causes thepackage articulation system on the autonomous vehicle to remove thepackage from within the package payload storage and place the package atthe transaction location.

In another embodiment, the third node may be further operative totransmit a verification message to the server over the longer rangecommunication interface, where the verification message confirms thatthe package was dropped off at the transaction location.

And in a more detailed embodiment, the second node associated with thepackage may be an ID node (another node of the plurality of nodes) andis operative to communicate with the mobile master node over theshort-range communication interface but is unable to directlycommunicate with the server.

Equipment Monitoring Applications

Embodiments of a wireless hierarchical node network may be furtherapplied to equipment monitoring situations where enhanced tracking andvisibility may be desired. In more detail, exemplary ID nodes, exemplarymaster nodes, and an exemplary server operating in a hierarchy as awireless node network provide the capacity for improved tracking andenhanced visibility to the location of items associated with such nodes(e.g., whether inside or outside of structures and containers). And whenleveraging the sensing capabilities of some of such exemplary nodes, itprovides the capacity to know what is going on with items to which theexemplary nodes are associated. For example, when a piece of equipmentis being monitored using such a hierarchical node network, themonitoring system is able to leverage this enhanced tracking andvisibility into what is going on and where to identify an actionableevent so that a responsive action may be taken at the appropriate timeand with the appropriate scope of action.

In a general embodiment, a piece of equipment may be any type of machineor apparatus where operation of the equipment is desired to bemonitored. For example, such equipment may include, but is not limitedto, medical equipment, office equipment, industrial equipment,manufacturing equipment, construction equipment, transportationequipment, laboratory equipment, sporting equipment, automotiveequipment, farm equipment, marine equipment, mining equipment, and thelike. While these examples are expressly noted here, those skilled inthe art will appreciate that principles of an embodiment may be equallyapplicable to other types of equipment where monitoring the location andoperation of that type of equipment may be desired.

FIG. 71 is a diagram illustrating an exemplary hierarchical node networkfor monitoring a piece of equipment within an exemplary healthcarefacility in accordance with an embodiment of the invention. The exampleenvironment illustrated in FIG. 71 is that of an exemplary healthcarefacility 7100, such as an urgent care facility where medical patientsmay arrive, seek urgent treatment by medical personnel, have treatmentusing medical equipment within the facility, and may leave to returnhome to their residence after receiving treatment.

Referring now to FIG. 71, exemplary healthcare facility 7100 is shownhaving several areas, such as a patient lobby 7105, an examination area7110, a confidential records room 7115, and a diagnostic testing room7125. A person, who may be considered a medical patient in a healthcarefacility or under treatment or medical care at their residence, mayenter facility 7100 through an entrance 7130. Once in the patient lobby7105, the patient may check in at the front desk area 7135, where theymay sign in and register, provide relevant information (e.g., name,billing information, contact information, and the like) and receive ahealthcare identification card.

In this example, the healthcare identification card may incorporate anID node 7120 a within it. However, in other examples, those skilled inthe art will appreciate that other items associated with the patient mayincorporate or otherwise include an ID node, such as clothing worn bythe patient, a medical identification bracelet or wristband provided byhealthcare facility personnel upon registering at desk area 7135, aclipboard type of device provided by the facility with relevantdocuments to be reviewed and used during the patient's visit to thefacility 7100, or an electronic user access device (such as a smartphonewith an app that enables operation of the smartphone to be that of an IDnode; or a tablet type device provided by the patient or facility with asimilar app running to enable operation as an ID node associated withthe patient).

Once the patient has checked in and after a wait in the patient lobby7105, the patient may be called back to the examination area 7100 (ornotified of this via the ID node's user interface, such as a light,sound, or simple alphanumeric display). The patient may enterexamination area 7105 through door 7140 for an initial examination ortriage examination by a medical technician 7175 using various medicalequipment, such as blood pressure monitor, a cardiac monitor, and apulse oximeter (each of which are associated with their own ID nodes7120 b-d). While not shown in FIG. 71, facility 7100 may also include astorage area where an inventory of different medical equipment may bestored (each piece of equipment having an ID node associated with it).

After having the preliminary testing done by medical technician 7175,the patient may move over to another part of the examination area 7100(which may be open or in closed off distinct examination rooms) forfurther examination by another healthcare provider 7180 (e.g., aphysician or nurse). If during the examination by the healthcareprovider 7180, it is determined that diagnostic testing may also beneeded to further diagnose the patient's symptoms and treat the patient,the patient may be directed to enter diagnostic testing room 7125. Oncein diagnostic testing room 7125, the patient may be instructed to laydown on testing table 7155 while another healthcare provider (e.g., aradiologist or x-ray technician) activates x-ray machine 7150 (which hasan ID node 7120 x associated with it). After the test, the patient maybe directed back to the examination area 7110 or back to the patientlobby 7105. However, if the patient's treatment is complete, the patientmay check out and leave the facility.

In some situations, the patient may not be familiar with the layout ofthe facility 7100 and wander into areas where the patient is notanticipated to be, such as the confidential records room 7115. Forexample, a patient 7170 may have an ID node 7120 e integrated into hermedical identification bracelet or wristband. The patient 7170 may havebeen in an automobile accident and had an x-ray on x-ray machine 7150operated by technician 7160. Given the x-ray testing confirmed a brokenankle and arm; a physician 7180 may have put her leg and arm in casts aspart of the treatment. The patient 7170 may be confused and, whileattempting to leave the examination area 7110, may have enteredconfidential records room 7115 where she is not anticipated norpermitted to be. As will be explained in more detail, the use of ID node7120 e here may proactively warn the patient as well as others that sheis located in an area where she is not anticipated to be.

More generally, in such an exemplary medical environment, the ID nodesmay be associated with a person or a piece of equipment and be operativeto monitor an activity of the person or an operation of the piece ofequipment. Additionally, those skilled in the art will appreciate basedon the prior discussion of exemplary ID nodes, master nodes, andservers, such ID nodes in this medical environment are operative tocommunicate directly with master node 7110 a but are unable to directlycommunicate with server 100. However, the master node 7110 a isoperative to directly communicate with the server 100 and separatelycommunicate with the ID nodes shown in FIG. 71. Those skilled in the artwill further appreciate the while only one master node 7110 a is shownin FIG. 71 for facility 7100, this is done for simplicity of explanationand that other embodiments may deploy one or more other master nodesthat are also operative to communicate directly with server 100 and eachother, as well as ID nodes that broadcast advertising signals within thereception range of the respective master nodes.

FIG. 72 is a flow diagram illustrating an exemplary method formonitoring a piece of equipment (e.g., a blood pressure monitor, a pulseoximeter, an x-ray machine, etc.) using a hierarchical node networkhaving at least an ID node, a master node, and a server in accordancewith an embodiment of the invention. Referring now to FIG. 72, method7200 begins at step 7205 with the master node associating with the IDnode when the master node detects a signal broadcast from the ID node.The ID node is associated with the piece of equipment, such as medicalequipment, office equipment, industrial equipment, manufacturingequipment, construction equipment, transportation equipment, laboratoryequipment, sporting equipment, automotive equipment, marine equipment,and mining equipment. These are examples of equipment where operationsmay be monitored. The ID node (such as ID node 7120 x shown in FIG. 71or exemplary ID node 120 a shown in FIG. 3) is operative to monitor anoperation of the piece of equipment and to communicate directly with themaster node but is unable to directly communicate with the server.However, the master node is operative to directly communicate with theserver and separately communicate with the ID node.

For example, as shown in FIG. 71, ID node 7120 x can monitor anoperation of the x-ray machine 7150 (e.g., when it was activated, whatoperation was performed, gather information from the machine on whichoperator or technician activated it, how long it was operated, andpatient information related to the test performed during the operationof the machine, etc.). In doing so, ID node 7120 x may be implemented asa type of sensor node having sensors or other interfacing circuitryonboard (and as explained with reference to exemplary ID node 120 a inFIG. 3) to gather information from x-ray machine 7150 and monitordesired operations of the machine 7150. ID node 7120 x can communicatedirectly with the master node 7110 a but is unable to directlycommunicate with the server 100 where master node 7110 a can directlycommunicate with the server 100 over a longer-range communication path(e.g., WIFI) and separately communicate with the ID node 7110 a over,for example, a shorter-range communication path (e.g., a Bluetooth®enabled communication path between Bluetooth® enabled devices).

In one embodiment, the associating step of method 7100 may furthercomprise establishing a passive association between the master node andthe ID node without requiring without requiring a prior authoritygranted by the server. However, in another embodiment, the associatingstep of method 7100 may further comprise establishing an activeassociation between the master node and the ID node. The activeassociation, in contrast to the passive association, reflects anauthorized connection between the master node and the ID node based uponan authority granted by the server. In one example, the master nodesends an association request to the server prior to associating themaster node and ID node associated with the piece of equipment. However,in other examples, such a request is made unnecessary if the serverpreauthorizes such an association. This avoids the need for the masternode to request the authority from the server after detecting the signalbroadcast from the ID node.

At step 7210, method 7200 continues with the server determining alocation of the ID node. The location of the ID node associated with thepiece of equipment may factor into what an actionable event is, whichmay require a responsive action to be taken. In more detail, the step ofdetermining the location of the ID node may further comprise trackingthe location of the ID node over time. And in even more detail, the stepof determining the location of the ID node may further comprise trackingthe location of the ID node over time and refining the location of theID node based upon context data related to an operating environment ofthe piece of equipment and the ID node

At step 7215, method 7200 continues with the ID node detecting anactionable event related to the operation of the piece of equipment. Inone embodiment, the ID node alone may detect the actionable event. Inanother embodiment, the ID node may detect a condition for theactionable event related to the equipment's operation and report thatcondition to the master node, which may either use that conditioninformation along with location information on the ID node to detect theactionable event or pass that condition information to the server wherethe actionable event may be detected using that condition informationand other information (such as location data or context data related tothe ID node or its operating environment).

In one or more detailed embodiments, method 7200 may detect anactionable event by detecting a movement status, an activation status,or a usage status related to the operation of the piece of equipment. Anexemplary movement status may be whether the ID node (and the piece ofequipment associated with it) was just moved, is not moving, or ismoving relative to a path or anticipated point(s). An exemplaryactivation status may be a detected power up of the equipment in generalor activation of a particular part of or feature used on the equipment.Those skilled in the art will appreciate that the level of granularityon such a detected activation will depend on the sophistication in theinterfacing circuitry on the ID node and the ability to receive ormonitor signals or environmental conditions related to the piece ofequipment itself.

At step 7220, method 7200 continues with the ID node transmitting amessage to the master node reporting the actionable event. At step 7225,method 7200 continues by notifying the server by the master node aboutthe actionable event. However, in embodiments where detection of theactionable event occurs at the master node level or the server level(based at least in part on the condition information), those skilled inthe art will appreciate there may be no need to transmit such a messageto the master node or notify the server if the master node about theactionable event. Instead, such embodiments may transmit a message tothe master node reporting the condition information, and the master nodemay then notify the server with that information.

At step 7230, method 7200 concludes with the server initiating aresponsive action based upon the notification. In one embodiment, thestep of initiating the responsive action step may comprise updating abilling attribute related to the operation of the piece of equipment.For example, the server may implement a billing system relating to useof the particular piece of equipment (such as a billing computer systemfor healthcare facility 7100) or the server may provide input to aseparate billing computer system. Such a billing attribute may, forexample, be in the form of an identification of the piece of equipmentand a cost to be billed for use of the equipment monitored by the IDnode.

In another embodiment, the step of initiating the responsive action stepmay comprise updating an inventory attribute related to the operation ofthe piece of equipment. Generally, the piece of equipment may be part ofa managed inventory of equipment where it is desired to track or monitordifferent aspects of the inventory, such as what is in the inventory,where the inventory is collectively located, and how the inventory isused and may be aging. An exemplary inventor attribute may includeinformation related to monitored aspects of the inventory (such as useof this piece of the equipment inventory, a location of this piece ofthe equipment inventory, and the like).

In still another embodiment, the step of initiating the responsiveaction step may comprise updating a maintenance attribute related to theoperation of the piece of equipment. For example, the piece of equipmentmay have a maintenance schedule that is setup for that particular piece.An exemplary maintenance attribute may include operational time as itrelates to such a maintenance schedule. Furthermore and more generally,an exemplary maintenance attribute to be updated may include informationrelated to any service, repairs, refurbishment, parts replacement, orother maintenance done on the equipment.

In yet another embodiment, the step of initiating the responsive actionstep may generally comprise updating a usage attribute related to theoperation of the piece of equipment. For example, this may generally betracking time of operation (more generally usage time) for the piece ofequipment. In another example, this may be monitored in more detail asto how modes of operation are enabled and used and for how long. Thus,an exemplary usage attribute may be a simple activation count but may bea snapshot of operations and all operational data generated when thepiece of equipment is used. Those skilled in the art will appreciatethat different embodiments may advantageously take advantage of the morecomplex implementations, despite the higher costs to do so andcomplexities at interfacing and storing such information sensed from theequipment by the ID node.

In a further embodiment, the step of initiating the responsive actionstep may comprise updating a quality assurance attribute related to theoperation of the piece of equipment. Many pieces of equipment are usedwhere the user is concerned about quality and the users employ qualityassurance programs to monitor and make sure operations are accurate andhave a high standard of quality. An exemplary quality assuranceattribute related to the operation of the piece of equipment may involvetracking and monitoring the output of the equipment to ensure that theequipment is running at an acceptable level (not providing erroneousresults, is operating in calibration, etc.).

In another embodiment of method 7200, the master node may avoid the needto immediately notify the server regarding the actionable event and maybe able to initiate a responsive action (such as that described above)prior to informing the server of the actionable event. Such anembodiment places more computational responsibility at the level of themaster node, but may provide a timing advantage by not requiringnotification of the server as a precondition for initiating theresponsive action.

Another embodiment includes a hierarchical node network for monitoring apiece of equipment. In this embodiment, the hierarchical node networkcomprises a server, a master node, and an ID node associated with apiece of equipment. The ID node is operative to monitor an operation ofthe piece of equipment, and can wirelessly communicate directly with themaster node over a shorter range communication path but is unable todirectly communicate with the server. The ID node is also operative todetect an actionable event related to the operation of the piece ofequipment, and transmit a message to the master node reporting theactionable event.

The master node in the hierarchical node network is operative todirectly wirelessly communicate with the server over a longer rangecommunication path, associate with the ID node upon detection of asignal broadcast from the ID node, and notify the server about theactionable event reported in the message received from the ID node. Theserver is then operative, as part of the hierarchical node network here,to determine a location of the ID node, receive the notification fromthe master node regarding the actionable event, and initiate aresponsive action based upon the notification. Thus, this embodiment andsimilar embodiments of the hierarchical node network for monitoring apiece of equipment may operate similar to that described above withrespect to the various embodiments and operations of method 7200.

Again, while embodiments of the method for monitoring a piece ofequipment and a hierarchical node network for monitoring a piece ofequipment are largely describe above with respect to medical equipmentin a medical or healthcare environment, such as that shown in FIG. 71,those skilled in the art will appreciate that the same principles may beapplied to different kinds of equipment, such as office equipment (e.g.,wirelessly monitoring use of toner in printers), industrial equipment(e.g., wirelessly monitoring the usage time for a turbine in a powerplant), manufacturing equipment (e.g., wirelessly monitoring operatortime on a welding machine), construction equipment (e.g., wirelesslylogging the use of transmission oil consumption in a dozer),transportation equipment (e.g., wirelessly monitoring tire pressures onan automated airport bus), laboratory equipment (e.g., wirelesslymonitoring use of a high energy output mode for a transmitter testrack), sporting equipment (e.g., wirelessly monitoring a number ofimpacts by an ID node embedded within an enhanced football helmet),automotive equipment (e.g., wirelessly monitoring use of a trailerhitch), farm equipment (e.g., wirelessly monitoring operator time on acombine harvester machine and where the combine harvester machine hasbeen gathering crops), marine equipment (e.g., wirelessly monitoringenergy expended by communications equipment onboard a marine vessel),and mining equipment (e.g., wirelessly monitoring use of fuel by a fleetof front-end loaders).

Personnel Monitoring Applications

Similar to embodiments related to equipment monitoring, embodiments of awireless hierarchical node network may be further applied to monitoringpeople (such as medical patients) as they move and for, in someinstances, quantifiable health characteristics of a person (such asheart rate, heart rhythm, blood pressure, blood sugar, respiration,blood gasses, and the like). Again, as noted above, exemplary ID nodes,exemplary master nodes, and an exemplary server may operate in ahierarchy as a wireless node network, which provides the capacity forimproved tracking and enhanced visibility to where people associatedwith such nodes are (whether inside or outside of facilities) and whatmay be going on with or to such people. And when leveraging the sensingcapabilities of some of such exemplary nodes (e.g., sensor nodes wherean ID node or master node also includes one or more sensors), itprovides the capacity to know what is going on with a person to whichthe exemplary nodes are associated. When a person is being monitoredusing such a hierarchical node network, the monitoring system is able toleverage this enhanced tracking and visibility into what is going onwhere and identify appropriate actionable events so that similarlyappropriate responsive actions may be taken at the appropriate time forthe person.

Referring back to the example healthcare facility illustrated in FIG.71, server 100 is connected via network 105 to facility master node 7110a. Some of the ID nodes shown in FIG. 71 may be associated with a personas they approach and enter the facility, and receive treatment there. Inone example, a patient is associated with an ID node typically uponentry to the facility. In more detail, a patient may have registered atdesk 7135 and was given a healthcare identification bracelet, wristband, or card with an integrated ID node 7120 a in it. In this example,the healthcare personnel operating desk 7135 may activate the ID node7120 a and initially have it associated with the patient. In anotherembodiment, the patient may be able to use their smartphone (a type ofuser access device) running a particular app as they approach and enterfacility 7100 so that the smartphone operates as the ID node 7120 aassociated with the person.

As shown in FIG. 71, that patient is currently located in the lobby area7105 of healthcare facility 7100 and has not yet been treated. However,another patient 7170 (associated with a healthcare identificationbracelet (or wristband) having integrated ID node 7120 e) has alreadybeen treated. Specifically, patient 7170 was registered, received thebracelet with integrated ID node 7120 e, was helped back to theexamination area 7110, examined by physician 7180, and had x-ray imagestaken of her leg and arm in the diagnostic testing room. Patient 7170then was treated in the examination area 7110 where her arm and leg wereput in casts given the x-ray imaging revealed broken bones in thoseareas. However, patient 7170 may be confused and, while attempting toleave the examination area 7110, may have entered confidential recordsroom 7115 where she is not anticipated to be. Indeed, by having apersonal ID node (i.e., an ID node associated with the person), thepatient's location may be monitored both indoors and outside by virtueof locating techniques and methods as applied using the wireless nodenetwork disclosed herein.

While FIG. 71 illustrates a medical environment of a healthcare facility(such as a hospital, doctor's office, urgent care facility, or dentaloffice), those skilled in the art will quickly appreciate that theprinciples and advantages of monitoring a person using an exemplarywireless node network are also available in environments such as aresidential environment. For example, the same principles and advantageof monitoring a person in a healthcare facility using an exemplarywireless node network may be applied when the person is at a residenceor other type of building or area (e.g., in an office building, amanufacturing or industrial facility, a school, a camp, a shoppingcenter or mall, a park, a restaurant, a stadium, a hotel, and the like)where components of the exemplary wireless network may be deployed inone or more embodiments.

FIG. 73 is a flow diagram illustrating an exemplary method formonitoring a person's activity using a hierarchical node network havingat least an ID node, a master node, and a server in accordance with anembodiment of the invention. Referring now to FIG. 73, method 7300begins at step 7305 with the master node associating with the ID nodewhen the master node detects a signal broadcast from the ID node. The IDnode, in method 7300, is associated with a person and operative tomonitor the activity of the person and to communicate directly with themaster node but is unable to directly communicate with the server. Themaster node, on the other hand, is operative to directly communicatewith the server and separately communicate with the ID node. Forexample, facility master node 7110 a can directly communicate with theserver 100 over network 105 and can separately communicate with ID nodeswithin its communication range.

In one embodiment, method 7300 may have these nodes associating byestablishing a passive association between the master node and the IDnode without requiring without requiring a prior authority granted bythe server. However, in another embodiment, method 7300 may have thenodes associating by establishing an active association between themaster node and the ID node. The active association reflects anauthorized connection between the master node and the ID node based uponan authority granted by the server. In a more detailed example, theauthorized connection between the master node and the ID node may bepreauthorized by the server to avoid the need for the master node torequest the authority from the server after detecting the signalbroadcast from the ID node.

At step 7310, method 7300 continues with the server determining alocation of the ID node. As discussed above in detail in various ways,the server (or master node in another embodiment) may determine thelocation of the ID node associated with the person. In more detail, thestep of determining the location of the ID node may further beaccomplished by tracking the location of the ID node over time andrefining the location of the ID node based upon context data related toan operating environment of the person and the ID node. For example, inthe illustrated healthcare facility environment shown in FIG. 71, suchexemplary context data may include dimensional and layout information onthe facility 7100, anticipated regions of the facility 7100 where apatient may be anticipated to be located and regions where the patientis not anticipated to be located (e.g., confidential records room 7115),where particular equipment may be located (e.g., the location of x-raymachine 7150 associated with ID node 7120 x), and signal degradationinformation on how a similar type of ID node may operate in a similarenvironment (e.g., taking account anticipated RF shielding effects orinterference effects from known other broadcasting nodes in the area).

At step 7315, method 7300 continues with the ID node detecting anactionable event related to the activity of the person based upon thelocation of the ID node. As similarly noted with respect to step 7215when monitoring a piece of equipment, the ID node alone may detect theactionable event at step 7315. In another embodiment, the ID node maydetect a condition for the actionable event related to the person'sactivity (e.g., a health related condition or activity level condition)and report that condition to the master node, which may either use thatcondition information along with location information on the personal IDnode to detect the actionable event or pass that condition informationto the server where the actionable event may be detected using thatcondition information and other information (such as location data orcontext data related to the ID node or its operating environment).

In a detailed embodiment, method 7300 may detect an actionable event bydetecting a movement status as the actionable event related to theactivity of the person based upon the location of the ID node.

In another embodiment, the person is a medical patient. In furtherembodiments, those skilled in the art will understand that the personmay be an office worker that works in and around an office building, aworker on a manufacturing line or within an industrial facility, afaculty or student working at or attending a school, a camp staff memberor camper at a camp, a shopper at a mall or other retail facility, adiner or staff at a restaurant, the staff or an event attendee at astadium, or a staff member or hotel guest at a hotel.

When the person associated with the ID node is a medical patient,another embodiment of method 7300 may have the patient located in ahealthcare facility and the ID node having been integrated into ahealthcare facility identification (such as a bracelet, wristband, IDcard, or clip-on tag to wear on the person). The ID node, in otherembodiments, may be incorporated into other items used by or carried bythe patient, such as a clipboard, carrying bag, hospital clothing, orthe like.

In this embodiment with the medical patient at the healthcare facility,method 7300 may detect the movement status, which may indicate themedical patient has left the healthcare facility based upon the locationof the ID node. While in some cases, leaving the healthcare facility isnormally anticipated after treatment, detection that the patient hasleft the facility may be unexpected in other cases where the patienthas, for example, registered to stay in the facility and has not beenchecked out or otherwise authorized to leave the facility (e.g., thepatient may not remember where they are or wake up with some confusionand mistakenly leave the facility).

In another example, the movement status may indicate the medical patienthas entered a certain part of the healthcare facility based upon thelocation of the ID node. That part of the healthcare facility may be alocation where the medical patient is not anticipated to be within thehealthcare facility, such as a restricted area. For example, as shown inFIG. 71, patient 7170 has mistakenly wandered into the confidentialrecords area 7115, which is an area that the patient 7170 is notanticipated to be located and an event calling for some responsiveaction.

Another embodiment may have the personal ID node implemented as a typeof mobile sensor node associated with the patient. Implementing the nodeas a possible sensor node may allow the node to sense a quantifiablehealth characteristic related to the health of the medical patient. Inmore detail, method 7300 may implement step 7315 as detecting theactionable event as including sensing the quantifiable healthcharacteristic using the mobile sensor node, and then detecting theactionable event when the sensed quantifiable health characteristicmeets a predetermined condition. For example, if the ID node can senseblood pressure, the actionable event to detect may be when the ID nodesenses that the patient's blood pressure is greater than a threshold (asthe predetermined condition). In another example, if the ID node cansense the patient's blood sugar level, the actionable even to detect maybe when the ID node senses that the patient's blood sugar level eitherexceeds an upper threshold or goes below a lower threshold (as a morecomplex type of predetermined condition). The use of such a mobilesensor node to sense quantifiable health characteristics is not limitedto use within a healthcare facility—those skilled in the art willappreciate that deploying such a node with a person as they go about avariety of daily activities with work, exercise, play, and rest mayprovide an extremely unobtrusive way to monitor the health of thepatient outside the confines of a healthcare facility yet have promptaccess to very current information and location data in case somethinggoes wrong (as defined by the predetermined condition).

At step 7320, method 7300 continues by transmitting, by the ID node tothe master node, a message reporting the actionable event. At step 7325,method 7300 continues by notifying the server by the master node aboutthe actionable event. However, in embodiments where detection of theactionable event may occur at the master node level or the server level(based at least in part on the condition information), those skilled inthe art will appreciate there may be no need to transmit such a messageto the master node or notify the server if the master node about theactionable event. Instead, such embodiments may transmit a message tothe master node reporting the condition information, and the master nodemay then notify the server with that information.

At step 7330, method 7300 concludes by initiating, by the server, aresponsive action based upon the notification. In one embodiment, thestep of initiating the responsive action may be accomplished with theserver notifying one or more user access devices associated with arelative of the medical patient and/or a healthcare provider affiliatedwith the healthcare facility. For example, server 100 may haveinformation on whom to contact in case of an actionable event, and beable to issue a call, text, or other warning or notification to theidentified smartphone of a relative or the patient's physician.

In another embodiment of method 7300, the master node may avoid the needto immediately notify the server at step 7325 regarding the actionableevent and may be able to initiate a responsive action (such as thatdescribed above) by the master node itself (to accomplish step 7330)prior to informing the server of the actionable event. Such anembodiment places more computational responsibility at the level of themaster node, but may provide a timing advantage by not requiringnotification of the server as a precondition for initiating theresponsive action.

In still another more detailed embodiment of method 7300, the server mayinitiate a responsive action by tracking the movements of the medicalpatient to determine a pattern of movement; correlating the determinedpattern of movement to a recorded change in patient behavior; andnotifying a user access device associated with a healthcare provideraffiliated with the healthcare facility, where the notificationindicates the relationship between the determined pattern of movementand the recorded change in patient behavior. For example, tracking themovements of a patient to determine and unobtrusively establish patternsof movement may help a healthcare facility identify that the patient maybe in the beginning or later phases of dementia or may help identify theextent of physical impairment being suffered by the patient.

As noted above, embodiments of method 7300 are applicable when theperson may an office worker that works in and around an office building,a worker on a manufacturing line or within an industrial facility, afaculty or student working at or attending a school, a camp staff memberor camper at a camp, a shopper at a mall or other retail facility, adiner or staff at a restaurant, the staff or an event attendee at astadium, or a staff member or hotel guest at a hotel.

In one embodiment where the person is a medical patient located at aresidence, rather than a healthcare facility, the actionable eventdetected may be a detected movement status in step 7315 where themovement status indicates the medical patient has left the residencebased upon the location of the ID node. In another example, the movementstatus may indicate the medical patient is not moving at all over aperiod of time, or may be moving with a pattern of movement indicativeof a medical condition (e.g., some type of physical impairment (such asa broken leg, a wheelchair that is not completely functional, etc.) orsome type of mental impairment (such as dementia, Alzheimer's Disease,etc.)).

And in the embodiment where the person is a medical patient located at aresidence, initiating the responsive action in step 7330 may involvehaving the server (or master node in some situations) notify a useraccess device associated with a relative of the medical patient and/or aparticular healthcare provider.

In addition to the various embodiments of method 7300, anotherembodiment describes the hierarchical node network for monitoring anactivity of a person. In this embodiment, the hierarchical node networkcomprises a server, a master node, and an ID node associated with aperson (also referred to here as a personal ID node and explained aboveas a sensor node in some embodiments). The ID node is operative towirelessly communicate directly with the master node over a shorterrange communication path but is unable to directly communicate with theserver.

The ID node is also operative to monitor the activity of the person,such as the person's location, a quantifiable characteristic of theperson (e.g., blood pressure via blood pressure sensors, respiration viaa respiration sensor coupled to the ID node, pulse via a pulse oximetrysensor, orientation of limbs or the head via accelerometer sensors onthe ID node, other physiological characteristics via one or morebiosensors coupled to or integrated into the ID node, etc.). As such,the ID node can detect an actionable event related to the activity ofthe person, and transmit a message to the master node reporting theactionable event.

The master node is operative to associate with the ID node upondetection of a signal broadcast from the ID node (such as an advertisingpacket message broadcast at a particular power level setting), andnotify the server about the actionable event reported in the messagereceived from the ID node. The server is operative to determine alocation of the ID node, receive the notification from the master noderegarding the actionable event, and initiate a responsive action basedupon the notification. Thus, this embodiment and similar embodiments ofthe hierarchical node network for monitoring an activity of a person mayoperate similar to that described above with respect to the variousembodiments and operations of method 7300.

Medical Treatment Application

Additional embodiments may use a hierarchical node network to enhancehow a healthcare facility may operate as it provides medical treatmentto patients. In particular, such embodiments may enhance the treatmentprocess for a patient as they arrive and move throughout the facility byhelping to initiate pre-staged preparations related to the medicaltreatment through the use of elements in a hierarchical node network.

In one example, referring back again to the healthcare facility 7100shown in FIG. 71, a patient may arrive with a user access device (suchas a smartphone or tablet) executing an app that has the deviceoperating as a node (e.g., an app having functionality similar to code325 as explained herein so that the device may operate as a type of IDnode; or an app having functionality similar to code 425 as explainedherein so that the device may operate as a type of master node that candirectly communicate with the server and separately communicate with theID node over a different communication path). The patient may havepreviously used the same or different user access device (e.g., theirhome computer) to locate a nearest health care facility associated withthe network, and is prompted to provide status information related tothe patient's upcoming visit.

Exemplary medical status information may include condition informationrelated to a current medical problem with which the patient needs helpand treatment at the facility. The exemplary condition informationprovided may include specifics on a symptom indication related to thehealth condition of the person. In other embodiments, exemplary statusinformation may include but is not limited to initial or updatedinsurance information related to the patient or a relative of thepatient, address information, information on reasons for the visit, thetype of physician to be seen (e.g., a general physician, an ERphysician, a specialist physician, such as an endocrinologist, etc.).

Such information may then be sent through the network to the server(e.g., through a direct connection from the user access device that isoperating as an ID node to the server, or through an indirect connectionto the server where the user access device connects and uploads thecondition information to one or more intermediate devices first). Thus,as the patient approaches the facility 7100, the patient's own ID node,such as a user access device operating as, for example, an ID node in anembodiment may associate with the facility's master node 7110 a. Thisuser access device may not necessarily be the same device used by thepatient to provide and upload the medical status information (such asthe patient's condition information).

By facilitating the early provision and relevant consideration of thismedical status information from a patient, an embodiment of thehierarchical node network may be able to track the location of thepatient as it initiates one or more appropriate pre-staged preparationsfor the patient's impending visit to the facility and treatment oncewithin the appropriate part of the facility. And the hierarchical nodenetwork's ability to track the patient's location as the patient moves(outside or indoors) also allows for adjustments to the pre-stagedpreparations, including adjustments made to better locate the patientbased on context data about, for example, the facility. Furthermore,embodiments may provide for a proactive and interactive engagement withthe patient prior to the patient's arrival at the healthcare facility,during the arrival and initial patient registration, and while thepatient moves about within the facility.

In more detail, once the patient arrives and moves towards aregistration desk, the patient's smartphone or other user access deviceoperating as an ID node may pre-store relevant insurance information tobe shared, as well as help facilitate an efficient co-pay paymenttransaction using node association (see, e.g., FIG. 36 and theaccompanying description of embodiments for conducting a paymenttransaction using node association). For example, a patient's medicalflex account system may stage credits on the patient's user accessdevice operating as an ID node to use as currency for such a co-paytransaction.

FIG. 74 is a flow diagram illustrating an exemplary method forinitiating a pre-staged preparation related to medical treatment to beprovided to a patient at a healthcare facility using a hierarchical nodenetwork in accordance with an embodiment of the invention. Referring nowto FIG. 74, method 7400 is described beginning at step 7405 where themaster node associates with the ID node when the master node detects asignal broadcast from the ID node as the patient approaches thehealthcare facility. Here, the ID node is associated with the patientseeking the medical treatment. For example, the ID node may be thepatient's smartphone (a type of user access device) or a tablet runninga particular app. The ID node can communicate directly with the masternode, which is operative to directly communicate with the server andseparately communicate with the ID node.

In another embodiment, the master node may receive an authorization fromthe server so that the master node may actively associate with the IDnode. The authorization may, for example, permit the master node and theID node to actively associate with each other prior to detecting thesignal broadcast from the ID node. Thus, a type of pre-authorizedassociation may be setup by the server. For example, if the patientseeking treatment at healthcare facility 7100 has uploaded theirrelevant condition information to server 100, server 100 may providefacility master node 7110 a with an authorization to associate with theID node associated with the patient as the server 100 may haveregistration information related to the patient that links the patientwith the ID node (e.g., the patient's smartphone or tablet devicerunning an app so that the patient's device operates as an ID node).

In a different embodiment, the master node may associate with the IDnode by establishing an active association between the master node andthe ID node when the master node detects the signal broadcast from theID node as the patient approaches the healthcare facility. In moredetail, the active association may reflect an authorized connectionbetween the master node and the ID node based upon the authorization.This authorized connection then provides a secure communication pathbetween the master node and the ID node for privately sharing databetween the master node and the ID node.

At step 7410, method 7400 continues with the master node receivingmedical status information securely transmitted by the ID node relatedto the patient. In more detail, the medical status information maycomprise condition information securely transmitted by the ID noderelated to a health condition of the patient. In more detail, thecondition information received may include at least a symptom indicationrelated to the health condition of the patient. For example, when thepatient arrives at facility 7100 and is approaching entrance 7130, thefacility master node 7110 a may receive condition information about thepatient that includes symptom information that the patient's left ankleis bruised, swollen, and tender. Other types of medical statusinformation may comprises at least one of new or updated insuranceinformation on the patient or a relative of the patient, addressinformation on the patient or relative of the patient, informationrelated to a reason for the patient visiting the healthcare facility(e.g., scheduled appointment, ER visit, lab work visit, symptominformation, etc.), and information related to a type of physiciananticipated to be seen by the patient while visiting the healthcarefacility (e.g., an internist, an endocrinologist, etc.)

At step 7415, method 7400 continues when the master node transmits themedical status information to the server. Transmitting the medicalstatus information received from the ID node may be accomplished in avariety of manners, such as, for example, by sending the exact medicalstatus information the master node received or, alternatively, sending asummary of the status information the master node received. Bytransmitting the medical status information to the server, the server isthen aware of what symptoms and/or other information describe thepatient's status or characterize the health condition of the patientprior to the visit.

At step 7420, method 7400 continues by determining, by the server, thelocation of the ID node. As discussed above in detail in various ways,the server (or master node in some embodiments of method 7400) maydetermine the location of the ID node associated with the patient. Inmore detail, the step of determining the location of the ID node mayfurther be accomplished by tracking the location of the ID node overtime and refining the location of the ID node based upon context datarelated to an operating environment of the patient and the ID node. Forexample, in the illustrated healthcare facility environment shown inFIG. 71, such exemplary context data may include dimensional and layoutinformation on the facility 7100, anticipated regions of the facility7100 where a patient may be anticipated to be located and regions wherethe patient is not anticipated to be located (e.g., confidential recordsroom 7115), where particular equipment may be located (e.g., thelocation of x-ray machine 7150 associated with ID node 7120 x), andsignal degradation information on how a similar type of ID node mayoperate in a similar environment (e.g., taking account anticipated RFshielding effects or interference effects from known other broadcastingnodes in the area).

In particular, another embodiment of method 7400 may have the step oflocating the ID node relying upon a changing power characteristic of theuser access device operating as the ID node. Specifically, locating theID node may comprise providing, by the server to the master node, aninstruction to change a power characteristic (such as the RF outputpower level of the advertising signal broadcast from the ID node) of theuser access device operating as the ID node, and having the master nodesend the instruction to the user access device operating as the ID node.

In a more detailed example, providing the instruction may beaccomplished by refining a level of the power characteristic to arefined value based upon context data related to an anticipatedoperating environment of the user access device operating as the IDnode. Then, the master node would provide the instruction to change thepower characteristic of the user access device operating as the ID nodeto the refined value. For example, the output power level of the ID nodemay be refined to a lower adjusted value based upon information that mayindicate there are a large number of ID nodes anticipated to beoperating around the ID node as it is anticipated to move within thefacility.

Another example may have the ID node instructed to change its RF outputpower level to a refined level to account for anticipated signaldegradation that may occur within particular parts of the facilitythrough which the ID node is predicted to move. More specifically, thestep of refining may be accomplished by refining the level of the powercharacteristic to the refined value based upon the context data relatedto the anticipated operating environment of the user access deviceoperating as the ID node as the user access device is anticipated tomove to a predicted location (such as a busy examination area 7110)within the healthcare facility when the predicted location is related tothe medical status information (e.g., condition information). Forexample, for the condition of a broken ankle or leg, the system mayanticipate that the ID node associated with the patient will be movingto the examination area 7110 and move to the x-ray testing room 7125.Thus, the master node 7110 a may refine the RF output level for ID node7120 e to a lower level as it moves through a crowded examination area7110, but then refine it to a higher level as the ID node 7120 e movesinto a predicted area, such as the x-ray testing room 7125, wheresignificant signal degradation by shielding may be anticipated. As such,embodiments may take advantage of one or more of the enhanced locatingtechniques as disclosed herein.

At step 7425, method 7400 concludes with the server (or in someembodiments, the master node) initiating a pre-staged preparationrelated to the patient visiting the healthcare facility for medicaltreatment based upon the determined location of the ID node and themedical status information. In a more detailed embodiment, theinitiating step in method 7400 may be accomplished by providing adirection message from the server to the master node. The directionmessage may include a set of directions for the patient to a predictedlocation within the healthcare facility based upon the determinedlocation of the ID node and the medical status information. For example,with the broken ankle patient discussed above, server 100 may coordinatewith master node 7110 a to provide a message to the patient's smartphone(operating as an ID node, such as ID node 7120 e) to apprise the patientof where to go and what to bring. Those skilled in the art willappreciate that other relevant information may be provided as part ofthe direction message for display on a user interface of the smartphone.

In another more detailed embodiment, the initiating step in method 7400may be implemented with the server accessing a record in a recorddatabase. While FIG. 5 illustrates exemplary server 100 as accessing onetype of database (e.g., a context data database), those skilled in theart will appreciate that other such databases (e.g., medical recorddatabases) may be available and accessible to server 100 or to otherdedicated database server systems that access such a record at thedirection and instruction of server 100. In this embodiment, the record(such as a medical record prepared and maintained by the healthcarefacility 7100, a health record prepared by the patient themselves, etc.)is related to the patient and found as being based upon the determinedlocation of the user access device operating as the ID node (e.g., thelocation of the ID node is near the x-ray diagnostic testing room 7125)and the medical status information (e.g., condition information on thetenderness and swelling of the patient's leg) so relevant imagingrecords related to the patient and, more specifically, the patient's legmay be accessed.

The accessed record may then be transmitted by the server to a useraccess device associated with a part of the healthcare facility relatedto the medical status information to pre-stage the accessed recordbefore the user access device operating as the ID node is located at thepart of the healthcare facility related to the medical statusinformation. Thus, back in example of the patient with the broken ankle,server 100 may transmit the accessed relevant imaging records to anoffice computer (not shown) or tablet device (not shown) operated by thex-ray technician 7160 in room 7125.

Furthermore, method 7400 may also include the step of adjusting thepre-staged preparation based upon an updated location of the patient.For example, as the patient moves through the examination area 7110 and7125 to receive treatment, the patient may have an updated location ofmoving back towards the examination area 7110. In this exemplaryembodiment, any pre-staged relevant prior imaging records may be sent toa computer or tablet (not shown) operated by physician 7180 in theexamination area. Thus, such a hierarchical node network may operate toprovide context-driven treatment of a patient.

In a further embodiment, a more interactive, two-way exchange ofinformation may be proactively employed as part of initiating suchpre-staged preparations. For example, the step of initiating thepre-staged preparation may further comprise providing a context-driveninquiry from the server to the master node. The context driven inquirymay include one or more pre-screening prompts for additional informationfrom the patient based upon the medical status information. With thecontext-driven inquiry from the server, the master node may then sendone or more pre-screening prompts to the user access device operating asthe ID node for display on a user interface of the user access device.Such pre-screening prompts allow for multiple exchanges of informationto facilitate a more active user or patient engagement. Such promptsmay, in one embodiment, ask pre-screening questions such as addressinformation, insurance information or updates, co-pay information,symptom information, or other additional status information that may berefined from the medical status information originally provided.

In this further embodiment of method 7400, the master node may thenreceive feedback from the user access device operating as the ID node,where the feedback provides enhanced medical status information (e.g.,more detailed condition information, updates to address and insuranceinformation, and the like). The master node may then transmit thefeedback to the server for use in refining the pre-staged preparationrelated to the patient visiting the healthcare facility for the medicaltreatment.

In addition to the various embodiments of method 7400, anotherembodiment describes the hierarchical node network for initiating one ormore pre-staged preparations related to medical treatment for a patientat a healthcare facility. In this embodiment, the hierarchical nodenetwork comprises a server, a master node, and an ID node associatedwith a person (also referred to here as a personal ID node and explainedabove as a user access device (such as a smartphone) operating as the IDnode). The ID node is operative to wirelessly communicate directly withthe master node over a shorter range communication path. Morespecifically and under control of software (such as an app thatimplements code 325), ID node is operative to broadcast a signal as thepatient approaches the healthcare facility, and securely transmitmedical status information (related to a health condition of thepatient) to the master node after associating with the master node.

The master node in the exemplary network is operative to detect thesignal broadcast from the ID node as the patient approaches thehealthcare facility, associate with the ID node upon detection of thesignal broadcast from the ID node, receive the medical statusinformation securely transmitted by the ID node, and notify the serverwith a message about the received medical status information.

The server in the exemplary network is operative to determine a locationof the ID node, receive the message from the master node regarding thereceived medical status information, and initiate one or more pre-stagedpreparations related to the patient visiting the healthcare facility forthe medical treatment based upon the determined location of the ID nodeand the received medical status information. Thus, this embodiment andsimilar embodiments of the hierarchical node network for initiating apre-staged preparation related to medical treatment to be provided to apatient at a healthcare facility may operate similar to that describedabove with respect to the various embodiments and operations of method7400.

In summary, it should be emphasized that the sequence of operations toperform any of the methods and variations of the methods described inthe embodiments herein are merely exemplary, and that a variety ofsequences of operations may be followed while still being true and inaccordance with the principles of the present invention.

At least some portions of exemplary embodiments outlined above may beused in association with portions of other exemplary embodiments tobetter manage and locate nodes in a wireless node network or use suchnodes and network elements as part of a hierarchical node network.Moreover, at least some of the exemplary embodiments disclosed hereinmay be used independently from one another and/or in combination withone another and may have applications to devices and methods notdisclosed herein. However, those skilled in the art will appreciate thatthe exemplary nodes described above as operating within an embodiment ofa wireless node network may be considered a system of different networkelements, such as nodes, network devices operating as nodes, and aserver.

Those skilled in the art will appreciate that embodiments may provideone or more advantages, and not all embodiments necessarily provide allor more than one particular advantage as set forth here. Additionally,it will be apparent to those skilled in the art that variousmodifications and variations can be made to the structures andmethodologies described herein. Thus, it should be understood that theinvention is not limited to the subject matter discussed in thedescription. Rather, the present invention, as recited in the claimsbelow, is intended to cover modifications and variations.

What is claimed:
 1. A method for multi-entity management of an ID nodedeployed with an item to be shipped in a wireless node network,comprising: associating the ID node with a first entity user accessdevice by generating first association data on the ID node, the firstassociation data reflecting a logical pairing of the ID node and thefirst entity user access device, the first entity user access deviceoperating as a master node in the network and is operative tocommunicate directly with a server in the network over a firstcommunication path and separately communicate with the ID node over asecond communication path, wherein the ID node is operative tocommunicate directly with the first entity user access device over thesecond communication path but is unable to directly communicate with theserver; providing, by the ID node to the associated first entity useraccess device, access to data collected by the ID node if authorized byan initial privilege, the initial privilege having been automaticallyprovided by the server to the first entity user access device before thefirst entity user access device is provided with access to the datacollected by the ID node and separately from an authorization toassociate with the ID node provided by the server to the first entityuser access device; associating the ID node with a shipping entitymaster node in the network by generating second association data on theID node, the second association data reflecting a logical pairing of theID node and the shipping entity master node; providing, by the ID nodeto the associated shipping entity master node, access to the datacollected by the ID node based upon a transferred privilege, thetransferred privilege provided by the server to the shipping entitymaster node during transit of the item to be shipped with which the IDnode is deployed; associating the ID node with a second entity useraccess device by generating third association data on the ID node, thethird association data reflecting a logical pairing of the ID node andthe second entity user access device; providing, by the ID node to theassociated second entity user access device, access to the datacollected by the ID node if authorized by a destination privilege, thedestination privilege provided by the server to the second entity useraccess device during transit of the item to be shipped with which the IDnode is deployed, wherein the destination privilege allows the secondentity user access device to access the data collected by the ID nodefrom the ID node over a short-range communication path and which thenallows the second entity user access device to provide the data accessedfrom the ID node to the server over a long-range communication path; andrequesting, by the ID node, a software update to program code stored onthe ID node from the server regardless of where the data collected bythe ID node is stored.
 2. The method of claim 1, wherein the initialprivilege comprises a paid privilege to access the data collected by theID node.
 3. The method of claim 1, wherein the initial privilegecomprises a paid privilege to be provided a location of the ID node. 4.The method of claim 1, wherein the initial privilege comprises a paidprivilege to track an item associated with the ID node over time.
 5. Themethod of claim 1, wherein the initial privilege comprises a privilegefor the first entity user access device to manage where the datacollected by the ID node is stored.
 6. The method of claim 5, whereinthe initial privilege comprises a paid privilege to have the datacollected by the ID node uploaded to the first entity user access deviceover the second communication path.
 7. The method of claim 5, whereinthe initial privilege comprises a paid privilege to have the datacollected by the ID node uploaded to the server from the first entityuser access device over the first communication path.
 8. The method ofclaim 1, wherein the destination privilege comprises a paid privilege toaccess any of the data collected by the ID node.
 9. The method of claim1, wherein the destination privilege comprises a paid privilege toaccess only a limited portion of the data collected by the ID node. 10.The method of claim 1 further comprising restricting, by the ID node,the first entity user access device from directly accessing the datacollected by the ID node after the ID node is associated with theshipping entity master node.
 11. The method of claim 1, wherein the datacollected by the ID node while the ID node is associated with theshipping entity master node remains owned by a shipping entity relatedto the shipping entity master node when the second entity user accessdevice is not authorized to access the data collected according to thedestination privilege.
 12. A non-transitory computer-readable mediumcontaining instructions which when executed on a processor performs amethod for multi-entity management of an ID node deployed with an itemto be shipped in a wireless node network, the method comprising:associating the ID node with a first entity user access device bygenerating first association data on the ID node, the first associationdata reflecting a logical pairing of the ID node and the first entityuser access device, the first entity user access device operating as amaster node in the network and is operative to communicate directly witha server in the network over a first communication path and separatelycommunicate with the ID node over a second communication path, whereinthe ID node is operative to communicate directly with the first entityuser access device over the second communication path but is unable todirectly communicate with the server; providing, by the ID node to theassociated first entity user access device, access to data collected bythe ID node if authorized by an initial privilege, the initial privilegehaving been automatically provided by the server to the first entityuser access device before the first entity access device is provide withaccess to the data collected by the ID node and separately from anauthorization to associate with the ID node provided by the server tothe first entity user access device; associating the ID node with ashipping entity master node in the network by generating secondassociation data on the ID node, the second association data reflectinga logical pairing of the ID node and the shipping entity master node;providing, by the ID node to the associated shipping entity master node,access to the data collected by the ID node based upon a transferredprivilege, the transferred privilege provided by the server to theshipping entity master node during transit of the item to be shippedwith which the ID node is deployed; associating the ID node with asecond entity user access device by generating third association data onthe ID node, the third association data reflecting a logical pairing ofthe ID node and the second entity user access device; providing, by theID node to the associated second entity user access device, access tothe data collected by the ID node if authorized by a destinationprivilege, the destination privilege provided by the server to thesecond entity user access device during transit of the item to beshipped with which the ID node is deployed, wherein the destinationprivilege allows the second entity user access device to access the datacollected by the ID node from the ID node over a short-rangecommunication path and which then allows the second entity user accessdevice to provide the data accessed from the ID node to the server overa long-range communication path; and requesting, by the ID node, anupdate to the instructions executed by the processor from the serverregardless of where the data collected by the ID node is stored.
 13. Thenon-transitory computer-readable medium of claim 12, wherein the initialprivilege comprises a paid privilege to access the data collected by theID node.
 14. The non-transitory computer-readable medium of claim 12,wherein the initial privilege comprises a paid privilege to be provideda location of the ID node.
 15. The non-transitory computer-readablemedium of claim 12, wherein the initial privilege comprises a paidprivilege to track an item associated with the ID node over time. 16.The non-transitory computer-readable medium of claim 12, wherein theinitial privilege comprises a privilege for the first entity user accessdevice to manage where the data collected by the ID node is stored. 17.The non-transitory computer-readable medium of claim 16, wherein theinitial privilege comprises a paid privilege to have the data collectedby the ID node uploaded to the first entity user access device over thesecond communication path.
 18. The non-transitory computer-readablemedium of claim 16, wherein the initial privilege comprises a privilegeto have the data collected by the ID node uploaded to the server fromthe first entity user access device over the first communication path.19. The non-transitory computer-readable medium of claim 12, wherein thedestination privilege comprises a paid privilege to access any of thedata collected by the ID node.
 20. The non-transitory computer-readablemedium of claim 12, wherein the destination privilege comprises a paidprivilege to access only a limited portion of the data collected by theID node.
 21. The non-transitory computer-readable medium of claim 12,wherein the method further comprises restricting, by the ID node, thefirst entity user access device from directly accessing the datacollected by the ID node after the ID node is associated with theshipping entity master node.
 22. The non-transitory computer-readablemedium of claim 12, wherein the data collected by the ID node while theID node is associated with the shipping entity master node remains ownedby a shipping entity related to the shipping entity master node when thesecond entity user access device is not authorized to access the datacollected according to the destination privilege.
 23. An ID nodedeployed with an item to be shipped and managed by multiple entitiesusing a wireless node network, the ID node comprising: a node processor;a node memory coupled to the processor, the memory maintaining code forexecution by the processor unit and data collected by the ID node duringoperations of the node; a short-range communication interface coupled tothe processing unit and operative to directly communicate with a masternode in the network over a short-range communication path but unable todirectly communicate with a server in the network; and wherein the nodeprocessor, when executing the code maintained on the node memory, isoperative to associate the ID node with a first entity user accessdevice by generating first association data in the node memory, thefirst association data reflecting a logical pairing of the ID node andthe first entity user access device, the first entity user access deviceoperating as the master node and being operative to communicate directlywith the server over a longer range communication path and separatelycommunicate with the ID node over the short-range communication path,provide the first entity user access device with access to the datacollected by the ID node if authorized by an initial privilege, theinitial privilege having been automatically provided by the server tothe first entity user access device before the first entity accessdevice is provided with access to the data collected by the ID node andseparately from an authorization to associate with the ID node providedby the server to the first entity user access device, associate the IDnode with a shipping entity master node in the network by generatingsecond association data in the node memory, the second association datareflecting a logical pairing of the ID node and the shipping entitymaster node, provide the associated shipping entity master node withaccess to the data collected by the ID node based upon a transferredprivilege, the transferred privilege provided by the server to theshipping entity master node during transit of the item to be shippedwith which the ID node is deployed, associate the ID node with a secondentity user access device by generating third association data in thenode memory, the third association data reflecting a logical pairing ofthe ID node and the second entity user access device, the second entityuser access device operating as another master node and being operativeto communicate directly with the server over the longer rangecommunication path and separately communicate with the ID node over theshort-range communication path, provide the associated second entityuser access device with access to the data collected by the ID node ifauthorized by a destination privilege, the destination privilegeprovided by the server to the second entity user access device duringtransit of the item to be shipped with which the ID node is deployed,wherein the destination privilege allows the second entity user accessdevice to access the data collected by the ID node from the ID node overa short-range communication path and which then allows the second entityuser access device to provide the data accessed from the ID node to theserver over a long-range communication path; and request a softwareupdate to the code maintained in the node memory from the serverregardless of where the data collected by the ID node is stored.
 24. TheID node of claim 23, wherein the initial privilege comprises a paidprivilege to access the data collected by the ID node.
 25. The ID nodeof claim 23, wherein the initial privilege comprises a paid privilege tobe provided a location of the ID node.
 26. The ID node of claim 23,wherein the initial privilege comprises a paid privilege to track anitem associated with the ID node over time.
 27. The ID node of claim 23,wherein the initial privilege comprises a privilege for the first entityuser access device to manage where the data collected by the ID node isstored.
 28. The ID node of claim 27, wherein the initial privilegecomprises a paid privilege to have the data collected by the ID nodeuploaded from the node memory to the first entity user access deviceover the short-range communication path via the short-rangecommunication interface.
 29. The ID node of claim 27, wherein theinitial privilege comprises a privilege to have the data collected bythe ID node uploaded to the server from the first entity user accessdevice over the longer range communication path.
 30. The ID node ofclaim 23, wherein the destination privilege comprises a paid privilegeto access any of the data collected by the ID node.
 31. The ID node ofclaim 23, wherein the destination privilege comprises a paid privilegeto access only a limited portion of the data connected by the ID node.32. The ID node of claim 23, wherein the node processor is furtheroperative to restrict the first entity user access device from directlyaccessing the node memory for the data collected by the ID node afterthe ID node is associated with the shipping entity master node.
 33. TheID node of claim 23, wherein the data collected by the ID node while theID node is associated with the shipping entity master node remains ownedby a shipping entity related to the shipping entity master node when thesecond entity user access device is not authorized to access the datacollected according to the destination privilege.